Merge branch 'master' into next

plugins/linkable_title.rb

@@ -6,9 +6,9 @@ module Jekyll
     end
 
     def render(context)
-      slug = @title.downcase.strip.gsub(' ', '-').gsub(/[^\w-]/, '')
+      title = Liquid::Template.parse(@markup).render context
-
+      slug = title.downcase.strip.gsub(' ', '-').gsub(/[^\w-]/, '')
-      "<a class='title-link' name='#{slug}' href='\##{slug}'></a> #{@title}"
+      "<a class='title-link' name='#{slug}' href='\##{slug}'></a> #{title}"
     end
   end
 end

sass/custom/_paulus.scss

@@ -403,4 +403,6 @@ p.note {
 
 .edit-github {
   text-align: right;
+  margin-bottom: 8px;
+  font-size: .8em;
 }

sass/oscailte/base/_navigation.scss

@@ -14,13 +14,14 @@ body{ -webkit-animation: bugfix infinite 1s; }
 #toggle, .toggle { display: none; }
 .menu li { list-style: none; float:left;  }
 
-$menu-collapse: 955px;
+$menu-collapse: 924px;
 
 // @media only screen and (max-width: $lap-end){
 @media only screen and (max-width: $menu-collapse){
   .menu { display: none; opacity: 0; width: 100%; position: absolute; right: 0; }
   .menu li { display: block; width: 100%; margin: 0; }
   .menu li a { display: block; width: 100%; text-decoration: none; -webkit-box-sizing: border-box; -moz-box-sizing: border-box; box-sizing: border-box; }
+  .menu li a .icon { display: none; }
   .toggle { display: block; position: relative; cursor: pointer; -webkit-touch-callout: none; -webkit-user-select: none; user-select: none; }
   #toggle:checked ~ .menu { display: block; opacity: 1; z-index: 999; }
 }
@@ -75,10 +76,10 @@ header .grid {
   @include box-sizing(border-box);
   @include transition(all 0.25s linear);
   display: block;
-  padding: 32px 20px;
+  padding: 32px 12px;
   text-decoration: none;
   font-weight: normal;
-  font-size: 16px;
+  font-size: 14px;
   line-height: 1;
 }
 
@@ -86,7 +87,7 @@ header .grid {
   background: $site-background;
   box-shadow: inset 0px 5px $navigation-color;
   color: $navigation-color;
-  padding: 40px 20px 24px;
+  padding: 40px 12px 24px;
 }
 
 .toggle{ 

source/_components/alarm_control_panel.alarmdotcom.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "Alarm.com Alarm Control Panel"
 description: "Instructions how to integrate Alarm.com into Home Assistant."
 date: 2016-01-14 22:00

source/_components/alarm_control_panel.manual.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "Manual Alarm Control Panel"
 description: "Instructions how to integrate manual alarms into Home Assistant."
 date: 2015-10-13 19:10

source/_components/alarm_control_panel.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "Alarm Control Panels"
 description: "Instructions how to integrate Alarm Control Panels into Home Assistant."
 date: 2015-10-13 19:10
@@ -12,6 +12,7 @@ footer: true
 
 Home Assistant can give you an interface with is similar to a classic alarm system. There are several panels supported:
 
+- [Alarm.com](/components/alarm_control_panel.alarmdotcom/)
 - [Manual](/components/alarm_control_panel.manual/)
 - [MQTT](/components/alarm_control_panel.mqtt/)
 - [Verisure](/components/verisure/)

source/_components/alarm_control_panel.mqtt.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "MQTT Alarm Control Panel"
 description: "Instructions how to integrate MQTT capable Alarm Panels into Home Assistant."
 date: 2015-09-14 19:10

source/_components/alexa.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "Alexa / Amazon Echo"
 description: "Instructions how to connect Alexa/Amazon Echo to Home Assistant."
 date: 2015-12-13 13:02

source/_components/arduino.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "Arduino"
 description: "Instructions how to setup an Arduino boards within Home Assistant."
 date: 2015-06-27 10:28
@@ -16,7 +16,7 @@ The [Arduino](https://www.arduino.cc/) device family are microcontroller boards
 
 There are a lot of extensions (so called [shields](https://www.arduino.cc/en/Main/ArduinoShields)) available. Those shields can be plugged-in into the existing connectors and stacked on top of each other. This makes it possible to expand the capabilities of the Arduino boards. 
 
-The arduino component is designed to let you use a directly attached board to your Home Assistant host over USB.
+The `arduino` component is designed to let you use a directly attached board to your Home Assistant host over USB.
 
 You need to have the [Firmata firmware](https://github.com/firmata/) on your board. Please upload the `StandardFirmata` sketch to your board, please refer to the [Arduino documentation](https://www.arduino.cc/en/Main/Howto) for further information.
 

source/_components/automation.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "Automation"
 description: "Instructions how to setup automation within Home Assistant."
 date: 2015-01-20 22:36

source/_components/binary_sensor.arest.markdown

@@ -1,6 +1,6 @@
 ---
-layout: component
+layout: page
-title: "aREST binary sensor"
+title: "aREST Binary Sensor"
 description: "Instructions how to integrate aREST binary sensors within Home Assistant."
 date: 2015-11-20 18:15
 sidebar: true
@@ -12,7 +12,7 @@ ha_category: Binary Sensor
 ---
 
 
-The arest binary sensor platform allows you to get all data from your devices (like Arduinos with a ethernet/wifi connection, the ESP8266, and the Raspberry Pi) running the [aREST](http://arest.io/) RESTful framework.
+The `arest` binary sensor platform allows you to get all data from your devices (like Arduinos with a ethernet/wifi connection, the ESP8266, and the Raspberry Pi) running the [aREST](http://arest.io/) RESTful framework.
 
 To use your aREST binary sensor in your installation, add the following to your `configuration.yaml` file:
 

source/_components/binary_sensor.command.markdown

@@ -1,6 +1,6 @@
 ---
-layout: component
+layout: page
-title: "Command line binary sensor"
+title: "Command line Binary Sensor"
 description: "Instructions how to integrate Command binary sensors within Home Assistant."
 date: 2016-01-13 12:15
 sidebar: true

source/_components/binary_sensor.http.markdown

@@ -0,0 +1,78 @@
+---
+layout: page
+title: "HTTP Binary Sensor"
+description: "Instructions how to integrate HTTP binary sensors within Home Assistant."
+date: 2016-02-05 12:15
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: http.png
+ha_category: Binary Sensor
+---
+
+The URL for a binary sensor looks like the example below:
+
+```bash
+http://IP_ADDRESS:8123/api/states/binary_sensor.DEVICE_NAME
+```
+
+<p class='note'>
+You should choose a unique device name (DEVICE_NAME) to avoid clashes with other devices.
+</p>
+
+The JSON payload must contain the new state and can have a friendly name. The friendly name is used in the frontend to name the sensor.
+
+```json
+{"state": "on", "attributes": {"friendly_name": "Radio"}}
+```
+
+For a quick test `curl` can be useful to "simulate" a device.
+
+```bash
+$ curl -X POST -H "x-ha-access: YOUR_PASSWORD" \
+    -d '{"state": "off", "attributes": {"friendly_name": "Radio"}}' \
+    http://localhost:8123/api/states/binary_sensor.radio
+```
+
+To check if the sensor is working, use again `curl` to retrieve the [current state](/developers/rest_api/#get-apistatesltentity_id).
+
+```bash
+$ curl -X GET -H "x-ha-access: YOUR_PASSWORD" \
+        http://localhost:8123/api/states/binary_sensor.radio
+{
+    "attributes": {
+        "friendly_name": "Radio"
+    },
+    "entity_id": "binary_sensor.radio",
+    "last_changed": "16:45:51 05-02-2016",
+    "last_updated": "16:45:51 05-02-2016",
+    "state": "off"
+}
+```
+
+## {% linkable_title Examples %}
+
+In this section you find some real life examples of how to use this sensor. Beside `curl`.
+
+### {% linkable_title Using Python request module %}
+
+As already shown on the [API](/developers/rest_api/) page, it's very simple to use Python and the [Requests](http://docs.python-requests.org/en/latest/) module for the interaction with Home Assistant.
+
+```python
+response = requests.post(
+        'http://localhost:8123/api/states/binary_sensor.radio',
+        headers={'x-ha-access': 'YOUR_PASSWORD', 'content-type': 'application/json'},
+        data=json.dumps({'state': 'on', 'attributes': {'friendly_name': 'Radio'}}))
+print(response.text)
+```
+
+### {% linkable_title Using `httpie` %}
+
+[`httpie`](https://github.com/jkbrzt/httpie) is a user-friendly CLI HTTP client.
+
+```bash
+$ http -v POST http://localhost:8123/api/states/binary_sensor.radio \
+      x-ha-access:YOUR_PASSWORD state=off \
+      attributes:='{"friendly_name": "Radio"}'
+```

source/_components/binary_sensor.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "Binary Sensor"
 description: "Instructions how to setup your binary sensors with Home Assistant."
 date: 2015-11-20 14:00

source/_components/binary_sensor.mqtt.markdown

@@ -1,6 +1,6 @@
 ---
-layout: component
+layout: page
-title: "MQTT binary sensor"
+title: "MQTT Binary Sensor"
 description: "Instructions how to integrate MQTT binary sensors within Home Assistant."
 date: 2015-05-30 23:21
 sidebar: true

source/_components/binary_sensor.nest.markdown

@@ -1,6 +1,6 @@
 ---
-layout: component
+layout: page
-title: "Nest binary sensor"
+title: "Nest Binary Sensor"
 description: "Instructions how to integrate Nest binary sensors within Home Assistant."
 date: 2016-01-26 08:00
 sidebar: true
@@ -12,7 +12,7 @@ ha_category: Binary Sensor
 ---
 
 
-The Nest binary sensor platform let you monitor various states of a thermostat from [Nest](https://nest.com).
+The `nest` binary sensor platform let you monitor various states of a thermostat from [Nest](https://nest.com).
 
 To set it up, add the following information to your `configuration.yaml` file:
 
@@ -21,18 +21,27 @@ sensor:
   platform: nest
   monitored_conditions:
     - 'fan'
-    - 'hvac_ac_state',
+    - 'hvac_ac_state'
-    - 'hvac_aux_heater_state',
+    - 'hvac_aux_heater_state'
-    - 'hvac_heat_x2_state',
+    - 'hvac_heat_x2_state'
-    - 'hvac_heat_x3_state',
+    - 'hvac_heat_x3_state'
-    - 'hvac_alt_heat_state',
+    - 'hvac_alt_heat_state'
-    - 'hvac_alt_heat_x2_state',
+    - 'hvac_alt_heat_x2_state'
-    - 'hvac_emer_heat_state',
+    - 'hvac_emer_heat_state'
     - 'online'
 ```
 
 Configuration variables:
 
 - **monitored_conditions** array (*Required*): States to monitor.
+  - 'fan'
+  - 'hvac_ac_state'
+  - 'hvac_aux_heater_state'
+  - 'hvac_heat_x2_state'
+  - 'hvac_heat_x3_state'
+  - 'hvac_alt_heat_state'
+  - 'hvac_alt_heat_x2_state'
+  - 'hvac_emer_heat_state'
+  - 'online'
 
-<p class='note'>You must have the [Nest component](https://home-assistant.io/components/nest/) configured to use this sensor.</p>
+<p class='note'>You must have the [Nest component](/components/nest/) configured to use this sensor.</p>

source/_components/binary_sensor.rest.markdown

@@ -1,6 +1,6 @@
 ---
-layout: component
+layout: page
-title: "RESTful binary sensor"
+title: "RESTful Binary Sensor"
 description: "Instructions how to integrate REST binary sensors into Home Assistant."
 date: 2015-12-17 19:10
 sidebar: true

source/_components/binary_sensor.rpi_gpio.markdown

@@ -1,6 +1,6 @@
 ---
-layout: component
+layout: page
-title: "Raspberry PI GPIO sensor"
+title: "Raspberry PI GPIO Binary Sensor"
 description: "Instructions how to integrate the GPIO sensor capability of a Raspberry PI into Home Assistant."
 date: 2015-08-30 19:00
 sidebar: true
@@ -12,7 +12,7 @@ ha_category: Sensor
 ---
 
 
-The rpi_gpio binary sensor platform allows you to read sensor values of the GPIOs of your [Raspberry Pi](https://www.raspberrypi.org/).
+The `rpi_gpio` binary sensor platform allows you to read sensor values of 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:
 

source/_components/binary_sensor.zigbee.markdown

@@ -1,6 +1,6 @@
 ---
-layout: component
+layout: page
-title: ZigBee Binary Sensor
+title: "ZigBee Binary Sensor"
 description: "Instructions on how to set up ZigBee binary sensors within Home Assistant."
 date: 2016-01-28 12:38
 sidebar: true

source/_components/browser.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "Browser"
 description: "Instructions how to setup the browser component with Home Assistant."
 date: 2015-01-24 14:39

source/_components/camera.foscam.markdown

@@ -1,6 +1,6 @@
 ---
-layout: component
+layout: page
-title: "Foscam IP camera"
+title: "Foscam IP Camera"
 description: "Instructions how to integrate Foscam IP cameras within Home Assistant."
 date: 2015-09-17 08:01
 sidebar: true
@@ -12,7 +12,7 @@ ha_category: Camera
 ---
 
 
-The foscam platform allows you to watch the live stream of your [Foscam](http://www.foscam.com/) IP camera in Home Assistant.
+The `foscam` platform allows you to watch the live stream of your [Foscam](http://www.foscam.com/) IP camera in Home Assistant.
 
 To enable your Foscam IP camera in your installation, add the following to your `configuration.yaml` file:
 

source/_components/camera.generic.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "Generic IP Camera"
 description: "Instructions how to integrate IP cameras within Home Assistant."
 date: 2015-07-11 0:36

source/_components/camera.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "Camera"
 description: "Instructions how to integrate cameras within Home Assistant."
 date: 2015-11-09 08:36

source/_components/camera.mjpeg.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "Generic MJPEG IP Camera"
 description: "Instructions how to integrate IP cameras within Home Assistant."
 date: 2015-11-09 08:36
@@ -11,7 +11,7 @@ ha_category: Camera
 ---
 
 
-The mjpeg component allows you to integrate IP cameras which are capable to  stream their video with MJPEG into Home Assistant.
+The `mjpeg` component allows you to integrate IP cameras which are capable to  stream their video with MJPEG into Home Assistant.
 
 To enable this sensor in your installation, add the following to your `configuration.yaml` file:
 

source/_components/configurator.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "Configurator"
 description: "Instructions how to integrate the configurator in your components."
 date: 2015-03-15 00:51

source/_components/conversation.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "Conversation"
 description: "Instructions how to have conversations with your Home Assistant."
 date: 2015-03-15 00:39

source/_components/device_sun_light_trigger.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "Presence based lights"
 description: "Instructions how to automate your lights with Home Assistant."
 date: 2015-01-20 22:36

source/_components/device_tracker.actiontec.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "Actiontec"
 description: "Instructions how to integrate Actiontec routers into Home Assistant."
 date: 2015-08-30 19:00

source/_components/device_tracker.aruba.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "Aruba"
 description: "Instructions how to integrate Aruba routers into Home Assistant."
 date: 2015-08-31 08:45

source/_components/device_tracker.asuswrt.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "ASUSWRT"
 description: "Instructions how to integrate ASUSWRT based routers into Home Assistant."
 date: 2015-08-06 19:00

source/_components/device_tracker.ddwrt.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "DD-WRT"
 description: "Instructions how to integrate DD-WRT based routers into Home Assistant."
 date: 2015-05-11 09:00

source/_components/device_tracker.fritz.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "FRITZ!Box"
 description: "Instructions how to integrate AVM FRITZ!Box based routers into Home Assistant."
 date: 2015-12-13 19:00
@@ -23,7 +23,7 @@ To use an Fritz!Box router in your installation, add the following to your `conf
 ```yaml
 # Example configuration.yaml entry
 device_tracker:
-  platform: asuswrt
+  platform: fritz
   host: YOUR_ROUTER_IP
   username: YOUR_ADMIN_USERNAME
   password: YOUR_ADMIN_PASSWORD

source/_components/device_tracker.icloud.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "iCloud"
 description: "Instructions how to use iCloud to track devices in Home Assistant."
 date: 2015-12-15 1000

source/_components/device_tracker.locative.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "Locative"
 description: "Instructions how to use Locative to track devices in Home Assistant."
 date: 2015-10-13 19:00

source/_components/device_tracker.luci.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "OpenWRT (luci)"
 description: "Instructions how to integrate OpenWRT routers into Home Assistant."
 date: 2015-03-23 19:59

source/_components/device_tracker.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "Device Tracker"
 description: "Instructions how to setup device tracking within Home Assistant."
 date: 2015-01-20 22:36

source/_components/device_tracker.mqtt.markdown

@@ -1,6 +1,6 @@
 ---
-layout: component
+layout: page
-title: "MQTT device tracker"
+title: "MQTT Device Tracker"
 description: "Instructions how to use MQTT to track devices in Home Assistant."
 date: 2015-09-19 20:41
 sidebar: true

source/_components/device_tracker.netgear.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "Netgear"
 description: "Instructions how to integrate Netgear routers into Home Assistant."
 date: 2015-03-23 19:59

source/_components/device_tracker.nmap_scanner.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "Nmap"
 description: "Instructions how to integrate Nmap into Home Assistant."
 date: 2015-03-23 19:59

source/_components/device_tracker.owntracks.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "Owntracks"
 description: "Instructions how to use Owntracks to track devices in Home Assistant."
 date: 2015-09-22 07:00

source/_components/device_tracker.snmp.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "SNMP"
 description: "Instructions how to integrate SNMP into Home Assistant."
 date: 2015-10-08 12:00

source/_components/device_tracker.thomson.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "Thomson"
 description: "Instructions how to integrate Thomson routers into Home Assistant."
 date: 2015-08-30 19:00

source/_components/device_tracker.tomato.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "Tomato"
 description: "Instructions how to integrate Tomato routers into Home Assistant."
 date: 2015-03-23 19:59

source/_components/device_tracker.tplink.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "TP-Link"
 description: "Instructions how to integrate TP-Link routers into Home Assistant."
 date: 2015-06-22 10:30

source/_components/device_tracker.ubus.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "OpenWRT (ubus)"
 description: "Instructions how to integrate OpenWRT routers into Home Assistant."
 date: 2015-03-23 19:59

source/_components/discovery.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "Discovery"
 description: "Instructions how to setup Home Assistant to discover new devices."
 date: 2015-01-24 14:39

source/_components/downloader.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "Downloader"
 description: "Instructions how to setup the downloader component with Home Assistant."
 date: 2015-01-24 14:39

source/_components/ecobee.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "Ecobee"
 description: "Instructions for how to integrate Ecobee thermostats and sensors within Home Assistant."
 date: 2015-11-30 17:54

source/_components/group.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "Group"
 description: "Instructions how to setup groups within Home Assistant."
 date: 2015-03-23 19:59

source/_components/history.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "History"
 description: "Instructions how to enable history support for Home Assistant."
 date: 2015-03-23 19:59
@@ -28,22 +28,22 @@ history:
 </p>
 
 <p class='note'>
-Events are saved in a local database. Google Graphs is used to draw the graph. Drawing is happening 100% in your browser - no data is transferred to anyone at any time.
+Events are saved in a local database. Google Graphs is used to draw the graph. Drawing is happening 100% in your browser. No data is transferred to anyone at any time.
 </p>
 
 #### {% linkable_title Implementation details %}
 
-The history is stored in a SQLite databse `home-assistant.db` within your config directory.
+The history is stored in a SQLite database `home-assistant.db` within your config directory.
 
- - events table is all events except time_changed that happened while recorder component was running.
+ - events table is all events except `time_changed` that happened while recorder component was running.
- - states table contains all the new_state values of state_changed events.
+ - states table contains all the `new_state` values of `state_changed` events.
  - Inside the states table you have:
-   - entity_id: the entity_id of the entity
+   - `entity_id`: the entity_id of the entity
-   - state: the state of the entity
+   - `state`: the state of the entity
-   - attributes: JSON of the state attributes
+   - `attributes`: JSON of the state attributes
-   - last_changed: timestamp last time the state has changed. A state_changed event can happen when just attributes change.
+   - `last_changed`: timestamp last time the state has changed. A state_changed event can happen when just attributes change.
-   - last_updated: timestamp anything has changed (state, attributes)
+   - `last_updated`: timestamp anything has changed (state, attributes)
-   - created: timestamp this entry was inserted into the database
+   - `created`: timestamp this entry was inserted into the database
 
 When the history component queries the states table it only selects states where the state has changed: `WHERE last_changed=last_updated`
 
@@ -55,3 +55,7 @@ SQLite databases do not support native dates. That's why all the dates are saved
 from datetime import datetime
 datetime.fromtimestamp(1422830502)
 ```
+
+#### {% linkable_title API %}
+
+The history information are also available through the [RESTful API](/developers/rest_api/#get-apihistory).

source/_components/http.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "HTTP"
 description: "Offers a web framework to serve files."
 date: 2015-12-06 21:35
@@ -25,9 +25,16 @@ http:
 
 Configuration variables:
 
-- **api_password** (*Optional*): Protect Home Assistant with a password
+- **api_password** (*Optional*): Protect Home Assistant with a password.
 - **server_port** (*Optional*): Let you set a port to use. Defaults to 8123.
 - **development** (*Optional*): Disable caching and load unvulcanized assets. Useful for Frontend development.
 - **ssl_certificate** (*Optional*): Path to your TLS/SSL certificate to serve Home Assistant over a secure connection.
 - **ssl_key** (*Optional*): Path to your TLS/SSL key to serve Home Assistant over a secure connection.
 
+On top of the `http` component is a [REST API](/developers/rest_api/) and a [Python API](/developers/python_api/) available.
+
+The `http` platforms are not a real platform within the meaning of the terminology used around Home Assistant. Home Assistant's [REST API](/developers/rest_api/) is consuming and proceeding messages received over HTTP. 
+
+To use those kind of sensors in your installation no configuration in Home Assistant is needed. All configuration is done on the devices themselves. This means that you must be able to edit the target URL or endpoint and the payload. The entity will be created after the first message has arrived.
+
+All [requests](/developers/rest_api/#post-apistatesltentity_id) needs to be sent to the endpoint of the device and must be **POST**.

source/_components/ifttt.manything.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "ManyThing"
 description: "Instructions how to setup ManyThing support with IFTTT."
 date: 2015-09-07 18:00

source/_components/ifttt.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "IFTTT"
 description: "Instructions how to setup IFTTT within Home Assistant."
 date: 2015-09-07 18:00

source/_components/influxdb.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "InfluxDB"
 description: "Record events in InfluxDB."
 date: 2015-12-06 13:08

source/_components/input_boolean.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "Input Boolean"
 description: "Instructions how to integrate the Input Boolean component into Home Assistant."
 date: 2016-01-17 16:58

source/_components/insteon_hub.markdown

@@ -1,6 +1,6 @@
 ---
-layout: component
+layout: page
-title: "Insteon"
+title: "Insteon Hub"
 description: "Instructions how to setup the Insteon Hub within Home Assistant."
 date: 2016-01-27 08:00
 sidebar: true
@@ -11,18 +11,22 @@ logo: insteon.png
 ha_category: Hub
 ---
 
-The `insteon` component let you use your [Insteon](http://www.insteon.com/) Hub with Home Assistant.
+The `insteon` component lets you use your [Insteon Hub](http://www.insteon.com/insteon-hub/) with Home Assistant.
 
-To integrate your Insteon hub with Home Assistant, add the following section to your `configuration.yaml` file:
+You will need to obtain an Insteon REST API key from the [Insteon Developer program](http://www.insteon.com/become-an-insteon-developer) to use this component.
+
+To integrate your Insteon Hub with Home Assistant, add the following section to your `configuration.yaml` file:
 
 ```yaml
 # Example configuration.yaml entry
-insteon:
+insteon_hub:
   username: YOUR_USERNAME
   password: YOUR_PASSWORD
+  api_key: YOUR_API_KEY
 ```
 
 Configuration variables:
 
-- **username** (*Required*): The username that used to access the Insteon interface.
+- **username** (*Required*): The username used to access the Insteon interface (e.g. the [connect.insteon.com](connect.insteon.com) site).
-- **password** (*Required*): The password that used to access the Insteon interface.
+- **password** (*Required*): The password used to access the Insteon interface.
+- **api_key** (*Required*): The Insteon REST API key emailed to you once you are approved in the Insteon Developer program.

source/_components/introduction.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "Introduction"
 description: "Details about the introduction within Home Assistant."
 date: 2015-10-25 15:15

source/_components/isy994.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "ISY994 Controller"
 description: "Instructions how to setup the ISY994 controller within Home Assistant."
 date: 2015-01-20 22:36

source/_components/keyboard.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "Keyboard"
 description: "Instructions how to simulate key presses with Home Assistant."
 date: 2015-01-24 14:39

source/_components/light.blinksticklight.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "Blinkstick"
 description: "Instructions how to setup Blinkstick lights within Home Assistant."
 date: 2015-10-08 10:00
@@ -12,7 +12,7 @@ ha_category: Light
 ---
 
 
-The blinkstick platform let you can control your [Blinkstick](https://www.blinkstick.com/) lights from within Home Assistant.
+The `blinkstick` platform let you can control your [Blinkstick](https://www.blinkstick.com/) lights from within Home Assistant.
 
 To add blinkstick to your installation, add the following to your `configuration.yaml` file:
 

source/_components/light.hue.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "Philips Hue"
 description: "Instructions how to setup Philips Hue within Home Assistant."
 date: 2015-03-23 20:09

source/_components/light.hyperion.markdown

@@ -1,6 +1,6 @@
 ---
-layout: component
+layout: page
-title: Hyperion
+title: "Hyperion"
 description: "Instructions how to integrate Hyperion into Home Assistant."
 date: 2015-10-25 22:43
 sidebar: true

source/_components/light.lifx.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "LIFX"
 description: "Instructions how to integrate LIFX into Home Assistant."
 date: 2016-01-27 08:00

source/_components/light.limitlessled.markdown

@@ -1,11 +1,10 @@
 ---
-layout: component
+layout: page
 title: "LimitlessLED"
 description: "Instructions on how to setup LimitlessLED within Home Assistant."
 date: 2015-12-03 13:00
 sidebar: true
 layout: page
-title: "LimitlessLED support"
 sidebar: false
 comments: false
 sharing: true

source/_components/light.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "Lights"
 description: "Instructions how to setup your lights with Home Assistant."
 date: 2015-01-24 14:39

source/_components/light.mqtt.markdown

@@ -1,6 +1,6 @@
 ---
-layout: component
+layout: page
-title: "MQTT light"
+title: "MQTT Light"
 description: "Instructions how to setup MQTT lights within Home Assistant."
 date: 2015-11-13 08:30
 sidebar: true

source/_components/light.rfxtrx.markdown

@@ -1,6 +1,6 @@
 ---
-layout: component
+layout: page
-title: "RFXtrx light"
+title: "RFXtrx Light"
 description: "Instructions how to integrate RFXtrx lights into Home Assistant."
 date: 2015-10-08 10:15
 sidebar: true
@@ -9,7 +9,8 @@ sharing: true
 footer: true
 ha_category: Light
 ---
-The rfxtrx platform support lights that communicate in the frequency range of 433.92 MHz.
+
+The `rfxtrx` platform support lights that communicate in the frequency range of 433.92 MHz.
 
 To enable RFXtrx lights in your installation, add the following to your `configuration.yaml` file:
 

source/_components/light.tellstick.markdown

@@ -1,6 +1,6 @@
 ---
-layout: component
+layout: page
-title: "TellStick light"
+title: "TellStick Light"
 description: "Instructions how to integrate TellStick lights into Home Assistant."
 date: 2015-08-06 19:00
 sidebar: true
@@ -12,7 +12,7 @@ ha_category: Light
 ---
 
 
-This tellstick light platform allows you to control your [TellStick](http://www.telldus.se/products/tellstick) dimmers.
+This `tellstick` light platform allows you to control your [TellStick](http://www.telldus.se/products/tellstick) dimmers.
 
 To use your TellStick device in your installation, add the following to your `configuration.yaml` file:
 

source/_components/light.vera.markdown

@@ -1,6 +1,6 @@
 ---
-layout: component
+layout: page
-title: "Vera light"
+title: "Vera Light"
 description: "Instructions how to integrate Vera lights into Home Assistant."
 date: 2015-10-20 21:00
 sidebar: true
@@ -12,7 +12,7 @@ ha_category: Light
 ---
 
 
-This vera light platform allows you to control your [Vera](http://getvera.com/) lights.
+This `vera` light platform allows you to control your [Vera](http://getvera.com/) lights.
 
 This platform is useful if you wish for switches connected to your Vera controller to appear as lights in Home Assistant. All switches will be added as a light unless you exclude them in the configuration file.
 

source/_components/light.wink.markdown

@@ -1,6 +1,6 @@
 ---
-layout: component
+layout: page
-title: "Wink light"
+title: "Wink Light"
 description: "Instructions how to setup the Wink lights within Home Assistant."
 date: 2015-01-20 22:36
 sidebar: true
@@ -12,6 +12,6 @@ ha_category: Light
 ---
 
 
-The wink sensor platform allows you to use your [Wink](http://www.wink.com/) lights.
+The wink light platform allows you to use your [Wink](http://www.wink.com/) lights.
 
 The requirement is that you have setup your [Wink hub](/components/light.wink/).

source/_components/light.zigbee.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: ZigBee Light
 description: "Instructions on how to set up ZigBee lights within Home Assistant."
 date: 2016-01-28 12:38

source/_components/light.zwave.markdown

@@ -1,6 +1,6 @@
 ---
-layout: component
+layout: page
-title: "Z-Wave light"
+title: "Z-Wave Light"
 description: "Instructions how to setup the Z-Wave lights within Home Assistant."
 date: 2015-11-11 13:00
 sidebar: true

source/_components/lock.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "Locks"
 description: "Instructions how to setup your locks with Home Assistant."
 date: 2015-11-21 08:10

source/_components/lock.wink.markdown

@@ -1,6 +1,6 @@
 ---
-layout: component
+layout: page
-title: "Wink lock"
+title: "Wink Lock"
 description: "Instructions how to setup the Wink locks within Home Assistant."
 date: 2015-11-20 12:00
 sidebar: true
@@ -12,7 +12,7 @@ ha_category: Lock
 ---
 
 
-The wink lock platform allows you to control your [Wink](http://www.wink.com/) locks.
+The Wink lock platform allows you to control your [Wink](http://www.wink.com/) locks.
 
 The requirement is that you have setup your [Wink hub](/components/wink/).
 

source/_components/logbook.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "Logbook"
 description: "Instructions how to enable the logbook component for Home Assistant."
 date: 2015-04-25 9:23

source/_components/logger.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "Logger"
 description: "Instructions how to enable the logger component for Home Assistant."
 date: 2015-11-12 17:00

source/_components/media_player.cast.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "Google Cast"
 description: "Instructions how to integrate Google Cast into Home Assistant."
 date: 2015-03-23 19:59

source/_components/media_player.denon.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "Denon Network Receivers"
 description: "Instructions how to integrate Denon Network Receivers into Home Assistant."
 date: 2015-09-08 09:00
@@ -12,7 +12,7 @@ ha_category: Media Player
 ---
 
 
-The denon platform allows you to control a [Denon Network Receivers](http://www.denon.co.uk/chg/product/compactsystems/networkmusicsystems/ceolpiccolo) from Home Assistant.
+The `denon` platform allows you to control a [Denon Network Receivers](http://www.denon.co.uk/chg/product/compactsystems/networkmusicsystems/ceolpiccolo) from Home Assistant.
 
 Supported devices:
 

source/_components/media_player.firetv.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "FireTV"
 description: "Instructions how to integrate Music Player Daemon into Home Assistant."
 date: 2015-10-23 18:00
@@ -12,7 +12,7 @@ ha_category: Media Player
 ---
 
 
-The firetv platform allows you to control a [Amazon Fire TV/stick](http://www.amazon.com/Amazon-DV83YW-Fire-TV/dp/B00U3FPN4U).
+The `firetv` platform allows you to control a [Amazon Fire TV/stick](http://www.amazon.com/Amazon-DV83YW-Fire-TV/dp/B00U3FPN4U).
 
 The python-firetv Python 2.x module with its helper script that exposes a HTTP server to fetch state and perform actions is used.
 

source/_components/media_player.itunes.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "iTunes"
 description: "Instructions how to integrate iTunes into Home Assistant."
 date: 2015-06-22 11:00

source/_components/media_player.kodi.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "Kodi"
 description: "Instructions how to integrate Kodi into Home Assistant."
 date: 2015-06-22 11:00
@@ -13,7 +13,7 @@ featured: true
 ---
 
 
-The kodi platform allows you to control a [Kodi](http://kodi.tv/) multimedia system from Home Assistant.
+The `kodi` platform allows you to control a [Kodi](http://kodi.tv/) multimedia system from Home Assistant.
 
 To add Kodi to your installation, add the following to your `configuration.yaml` file:
 

source/_components/media_player.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "Media Player"
 description: "Instructions how to setup your media players with Home Assistant."
 date: 2015-01-24 14:39

source/_components/media_player.mpd.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "Music Player Daemon (MPD)"
 description: "Instructions how to integrate Music Player Daemon into Home Assistant."
 date: 2015-06-02 08:00
@@ -12,7 +12,7 @@ ha_category: Media Player
 ---
 
 
-The mpd platform allows you to control a [Music Player Daemon](http://www.musicpd.org/) from Home Assistant. Unfortunatly you will not be able to manipulate the playlist (add or delete songs) or add transitions between the songs. 
+The `mpd` platform allows you to control a [Music Player Daemon](http://www.musicpd.org/) from Home Assistant. Unfortunatly you will not be able to manipulate the playlist (add or delete songs) or add transitions between the songs. 
 
 To add MPD to your installation, add the following to your `configuration.yaml` file:
 

source/_components/media_player.plex.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "Plex"
 description: "Instructions how to integrate Plex into Home Assistant."
 date: 2015-10-05 21:21

source/_components/media_player.sonos.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "Sonos"
 description: "Instructions how to integrateSonos devices into Home Assistant."
 date: 2015-09-12 13:00
@@ -13,7 +13,7 @@ featured: true
 ---
 
 
-The sonos platform allows you to control your [Sonos](http://www.sonos.com) HiFi wireless speakers and audio components from Home Assistant.
+The `sonos` platform allows you to control your [Sonos](http://www.sonos.com) HiFi wireless speakers and audio components from Home Assistant.
 
 To add your Sonos components to your installation, add the following to your `configuration.yaml` file.  It will perform auto-discovery of your connected speakers.
 

source/_components/media_player.squeezebox.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "Logitech Squeezebox"
 description: "Instructions on how to integrate a Logitech Squeezebox player into Home Assistant."
 date: 2015-08-09 11:00

source/_components/media_player.universal.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "Universal"
 description: "Instructions how to create a universal media player in Home Assistant."
 date: 2016-01-12 22:00

source/_components/modbus.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "Modbus"
 description: "Instructions how to integrate Modbus within Home Assistant."
 date: 2015-04-25 9:16

source/_components/mqtt.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "MQTT"
 description: "Instructions how to setup MQTT within Home Assistant."
 date: 2015-08-07 18:00

source/_components/mqtt_eventstream.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "MQTT Eventstream"
 description: "Instructions how to setup MQTT eventstream within Home Assistant."
 date: 2016-01-13 08:00

source/_components/mysensors.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "MySensors"
 description: "Instructions how to integrate MySensors sensors into Home Assistant."
 date: 2015-05-14 21:57

source/_components/nest.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "Nest"
 description: "Instructions how to integrate Nest into Home Assistant."
 date: 2016-01-29 21:57

source/_components/notify.file.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "File"
 description: "Instructions how to add file notifications to Home Assistant."
 date: 2015-06-22 10:00
@@ -11,7 +11,7 @@ ha_category: Notifications
 ---
 
 
-The file platform allows you to store notifications from Home Assistant as a file.
+The `file` platform allows you to store notifications from Home Assistant as a file.
 
 To enable file notifications in your installation, add the following to your `configuration.yaml` file:
 

source/_components/notify.free_mobile.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "Free Mobile"
 description: "Instructions how to add user notifications to Home Assistant."
 date: 2016-01-12 08:36

source/_components/notify.google_voice.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "Google Voice SMS"
 description: "Instructions how to add user notifications to Home Assistant."
 date: 2016-01-29

source/_components/notify.instapush.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "Instapush"
 description: "Instructions how to add Instapush notifications to Home Assistant."
 date: 2015-05-01 18:00
@@ -12,7 +12,7 @@ ha_category: Notifications
 ---
 
 
-The instapush platform uses [Instapush](https://instapush.im) to delivery notifications from Home Assistant to your Android or iOS device.
+The `instapush` platform uses [Instapush](https://instapush.im) to delivery notifications from Home Assistant to your Android or iOS device.
 
 The Instapush [Getting Started page](https://instapush.im/home/start/) will guide through the process of creating the required items.
 

source/_components/notify.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "Notifications"
 description: "Instructions how to add user notifications to Home Assistant."
 date: 2015-01-20 22:36

source/_components/notify.mqtt.markdown

@@ -0,0 +1,33 @@
+---
+layout: page
+title: "MQTT Notifications"
+description: "Instructions how to add MQTT notifications to Home Assistant."
+date: 2016-02-01 08:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: mqtt.png
+ha_category: Notifications
+---
+
+The MQTT notification support is different than the other [notification](/components/notify/) platforms. It is a service. This means that you don't have to create a configuration entry but you need to provide more details while calling the service.
+
+**Call Service** section from the **Developer Tools** allows you to send MQTT messages. Choose *mqtt/publish*  from the list of **Available services:** and enter something like the sample below into the **Service Data** field and hit **CALL SERVICE**.
+
+```json
+{"payload": "Test message from HA", "topic": "home/notification", "qos": 0, "retain": 0}
+```
+
+<p class='img'>
+<img src='/images/screenshots/mqtt-notify.png' />
+</p>
+
+Using the [REST API](/developers/rest_api/#post-apiservicesltdomainltservice) to send a message to a given topic.
+
+```bash
+$ curl -X POST -H "x-ha-access: YOUR_PASSWORD" \
+       -d '{"payload": "Test message from HA", "topic": "home/notification"}' \
+       http://IP_ADDRESS:8123/api/services/mqtt/publish
+```
+

source/_components/notify.nma.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "Notify My Android"
 description: "Instructions how to add user notifications to Home Assistant."
 date: 2015-05-01 18:00

source/_components/notify.pushbullet.markdown

@@ -1,5 +1,5 @@
 ---
-layout: component
+layout: page
 title: "PushBullet"
 description: "Instructions how to add user notifications to Home Assistant."
 date: 2015-01-20 22:36