home-assistant · NextNebula · Jan 30, 2016 · Jan 30, 2016 · Jan 30, 2016 · Jan 30, 2016
diff --git a/sass/custom/_paulus.scss b/sass/custom/_paulus.scss
@@ -403,4 +403,6 @@ p.note {
 
 .edit-github {
   text-align: right;
+  margin-bottom: 8px;
+  font-size: .8em;
 }
diff --git a/source/_components/alarm_control_panel.markdown b/source/_components/alarm_control_panel.markdown
@@ -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/)

diff --git a/source/_components/arduino.markdown b/source/_components/arduino.markdown
@@ -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.
 

diff --git a/source/_components/binary_sensor.arest.markdown b/source/_components/binary_sensor.arest.markdown
@@ -1,6 +1,6 @@
 ---
 layout: component
-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:
 

diff --git a/source/_components/binary_sensor.command.markdown b/source/_components/binary_sensor.command.markdown
@@ -1,6 +1,6 @@
 ---
 layout: component
-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

diff --git a/source/_components/binary_sensor.http.markdown b/source/_components/binary_sensor.http.markdown
@@ -0,0 +1,78 @@
+---
+layout: component
+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"}'
+```
diff --git a/source/_components/binary_sensor.mqtt.markdown b/source/_components/binary_sensor.mqtt.markdown
@@ -1,6 +1,6 @@
 ---
 layout: component
-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

diff --git a/source/_components/binary_sensor.nest.markdown b/source/_components/binary_sensor.nest.markdown
@@ -1,6 +1,6 @@
 ---
 layout: component
-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_aux_heater_state',
-    - 'hvac_heat_x2_state',
-    - 'hvac_heat_x3_state',
-    - 'hvac_alt_heat_state',
-    - 'hvac_alt_heat_x2_state',
-    - 'hvac_emer_heat_state',
+    - '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'
 ```
 
 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>
diff --git a/source/_components/binary_sensor.rest.markdown b/source/_components/binary_sensor.rest.markdown
@@ -1,6 +1,6 @@
 ---
 layout: component
-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

diff --git a/source/_components/binary_sensor.rpi_gpio.markdown b/source/_components/binary_sensor.rpi_gpio.markdown
@@ -1,6 +1,6 @@
 ---
 layout: component
-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:
 

diff --git a/source/_components/binary_sensor.zigbee.markdown b/source/_components/binary_sensor.zigbee.markdown
@@ -1,6 +1,6 @@
 ---
 layout: component
-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

diff --git a/source/_components/camera.foscam.markdown b/source/_components/camera.foscam.markdown
@@ -1,6 +1,6 @@
 ---
 layout: component
-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:
 

diff --git a/source/_components/camera.mjpeg.markdown b/source/_components/camera.mjpeg.markdown
@@ -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:
 

diff --git a/source/_components/device_tracker.fritz.markdown b/source/_components/device_tracker.fritz.markdown
@@ -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

diff --git a/source/_components/device_tracker.mqtt.markdown b/source/_components/device_tracker.mqtt.markdown
@@ -1,6 +1,6 @@
 ---
 layout: component
-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

diff --git a/source/_components/history.markdown b/source/_components/history.markdown
@@ -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.
- - states table contains all the new_state values of state_changed events.
+ - 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.
  - Inside the states table you have:
-   - entity_id: the entity_id of the entity
-   - state: the state of the entity
-   - 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_updated: timestamp anything has changed (state, attributes)
-   - created: timestamp this entry was inserted into the database
+   - `entity_id`: the entity_id of the entity
+   - `state`: the state of the entity
+   - `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_updated`: timestamp anything has changed (state, attributes)
+   - `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).
diff --git a/source/_components/http.markdown b/source/_components/http.markdown
@@ -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**.
diff --git a/source/_components/insteon_hub.markdown b/source/_components/insteon_hub.markdown
@@ -1,6 +1,6 @@
 ---
 layout: component
-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.
-- **password** (*Required*): The password 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 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.
diff --git a/source/_components/light.blinksticklight.markdown b/source/_components/light.blinksticklight.markdown
@@ -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:
 

diff --git a/source/_components/light.hyperion.markdown b/source/_components/light.hyperion.markdown
@@ -1,6 +1,6 @@
 ---
 layout: component
-title: Hyperion
+title: "Hyperion"
 description: "Instructions how to integrate Hyperion into Home Assistant."
 date: 2015-10-25 22:43
 sidebar: true

diff --git a/source/_components/light.limitlessled.markdown b/source/_components/light.limitlessled.markdown
@@ -5,7 +5,6 @@ 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

diff --git a/source/_components/light.mqtt.markdown b/source/_components/light.mqtt.markdown
@@ -1,6 +1,6 @@
 ---
 layout: component
-title: "MQTT light"
+title: "MQTT Light"
 description: "Instructions how to setup MQTT lights within Home Assistant."
 date: 2015-11-13 08:30
 sidebar: true
-Original file line number
+Diff line change
@@ Expand Up / @@ -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:
@@ Expand Down @@