home-assistant · balloob · Feb 13, 2016 · Jan 31, 2016 · Feb 1, 2016 · Feb 1, 2016
diff --git a/source/_components/alarm_control_panel.nx584.markdown b/source/_components/alarm_control_panel.nx584.markdown
@@ -0,0 +1,29 @@
+---
+layout: page
+title: "NX584 Alarm Control Panel"
+description: "Instructions how to integrate NX584 into Home Assistant."
+date: 2016-02-07 10:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: networx.png
+ha_category: Alarm
+---
+
+The `nx584` platform provides integration with GE, Caddx, Interlogix (and other brands) alarm panels that support the NX584 interface module (or have it built in). Supported panels include NX4/6/8/8E. Actual integration is done through [pynx584](http://github.com/kk7ds/pynx584) which is required for this to work.
+
+
+To enable this, add the following lines to your `configuration.yaml`:
+
+```yaml
+# Example configuration.yaml entry
+alarm_control_panel:
+  platform: nx584
+  host: ADDRESS
+```
+
+Configuration variables:
+
+- **host** (*Optional*): This is the host connection string (host:port) for the nx584 server process. If unset, it is assumed to be `localhost:5007`, which will work if the server process is running on the same system as home-assistant.
+
diff --git a/source/_components/apcupsd.markdown b/source/_components/apcupsd.markdown
@@ -0,0 +1,35 @@
+---
+layout: page
+title: "APCUPSd"
+description: "Instructions on how to integrate APCUPSd status with Home Assistant."
+date: 2016-02-10 17:11
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: apcupsd.png
+ha_category: Hub
+---
+
+[APCUPSd](http://www.apcupsd.org/) status information can be integrated into Home Assistant when the Network Information Server (NIS) [is configured](http://www.apcupsd.org/manual/manual.html#nis-server-client-configuration-using-the-net-driver).
+
+Create an `apcupsd` section in your configuration, optionally containing the following parameters:
+
+- **host**: The hostname/IP address on which the APCUPSd NIS is being served. Default: `localhost`
+- **port**: The port on which the APCUPSd NIS is listening. Default: `3551`
+
+#### Example
+
+Use defaults:
+
+```yaml
+apcupsd:
+```
+
+Set parameters:
+
+```yaml
+apcupsd:
+  host: 192.168.1.10
+  port: 1234
+```
diff --git a/source/_components/binary_sensor.apcupsd.markdown b/source/_components/binary_sensor.apcupsd.markdown
@@ -0,0 +1,22 @@
+---
+layout: page
+title: APCUPSd Binary Sensor
+description: "Instructions on how to set up an APCUPSd binary sensor within Home Assistant."
+date: 2016-02-10 18:47
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: apcupsd.png
+ha_category: Binary Sensor
+---
+
+In addition to the [APCUPSd Sensor](/components/sensor.apcupsd/) devices, you may also create a device which is simply `on` when the UPS status is `ONLINE` and `off` at all other times.
+
+#### Example
+
+```yaml
+binary_sensor:
+  - name: UPS Online
+    platform: apcupsd
+```
diff --git a/source/_components/bloomsky.markdown b/source/_components/bloomsky.markdown
@@ -0,0 +1,27 @@
+---
+layout: page
+title: "BloomSky"
+description: "Instructions how to integrate the BloomSky within Home Assistant."
+date: 2016-02-03 20:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: bloomsky.png
+ha_category: Hub
+---
+
+
+The `bloomsky` component allows you to access your [BloomSky](http://www.insteon.com/) weather station's [sensors](/components/sensor.bloomsky) and [camera](/components/camera.bloomsky) from Home Assistant.
+
+To integrate your BloomSky hub with Home Assistant, add the following section to your `configuration.yaml` file:
+
+```yaml
+# Example configuration.yaml entry
+bloomsky:
+  api_key: YOUR_API_KEY
+```
+
+Configuration variables:
+
+- **api_key** *Required*: Your BloomSky API key, obtained from your [BloomSky dashboard](https://dashboard.bloomsky.com) (click `developers` in the bottom left of the screen)
diff --git a/source/_components/camera.bloomsky.markdown b/source/_components/camera.bloomsky.markdown
@@ -0,0 +1,23 @@
+---
+layout: page
+title: "BloomSky Camera"
+description: "Instructions how to integrate the BloomSky camera within Home Assistant."
+date: 2016-02-03 20:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: bloomsky.png
+ha_category: Camera
+---
+
+
+The `bloomsky` camera component allows you to view the current photo created by the camera in the [BloomSky](https://www.bloomsky.com) weather station. This can work in concert with [BloomSky sensors](/components/sensor.bloomsky).
+
+To enable this camera in your installation, set up the [BloomSky component](/components/bloomsky) with your API key and add the following to your `configuration.yaml` file:
+
+```yaml
+# Example configuration.yaml entry
+camera:
+  platform: bloomsky
+```
diff --git a/source/_components/camera.uvc.markdown b/source/_components/camera.uvc.markdown
@@ -0,0 +1,33 @@
+---
+layout: page
+title: "UniFi Video Camera"
+description: "Instructions how to integrate UVC cameras within Home Assistant."
+date: 2016-02-07 10:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: ubiquiti.png
+ha_category: Camera
+---
+
+
+The `uvc` component allows you to integrate [UniFi Video Camera (UVC)](https://www.ubnt.com/unifi-video/unifi-video-camera/) into Home Assistant.
+
+To enable a UVC camera in your installation, add the following to your `configuration.yaml` file:
+
+```yaml
+# Example configuration.yaml entry
+camera:
+  platform: uvc
+  nvr: IP_ADDRESS
+  port: PORT
+  key: APIKEY
+```
+
+Configuration variables:
+
+- **nvr** *Optional*: The IP or hostname of the NVR (Network Video Recorder) server.
+- **port** *Optional*: The port number to use for accessing the NVR.
+- **key** *Required*: The API key available from the NVR web interface.
+
diff --git a/source/_components/garage_door.markdown b/source/_components/garage_door.markdown
@@ -0,0 +1,12 @@
+---
+layout: page
+title: "Garage door"
+description: "Instructions how to integrate Garage doors into Home Assistant."
+date: 2016-02-12 07:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+---
+
+Home Assistant can give you an interface to control any garage door.
diff --git a/source/_components/garage_door.wink.markdown b/source/_components/garage_door.wink.markdown
@@ -0,0 +1,18 @@
+---
+layout: page
+title: "Wink Garage door"
+description: "Instructions how to setup the Wink garage doors within Home Assistant."
+date: 2016-02-12 07:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: wink.png
+ha_category: Garage Door
+---
+
+
+The Wink garage door platform allows you to control your [Wink](http://www.wink.com/) enabled garage door.
+
+The requirement is that you have setup your [Wink hub](/components/light.wink/).
+
diff --git a/source/_components/influxdb.markdown b/source/_components/influxdb.markdown
@@ -23,6 +23,8 @@ influxdb:
   database: DB_TO_STORE_EVENTS
   username: MY_USERNAME
   password: MY_PASSWORD
+  ssl: true
+  verify_ssl: true
 ```
 
 Configuration variables:
@@ -32,4 +34,5 @@ Configuration variables:
 - **database** (*Optional*): Name of the database to use. Defaults to `home_assistant`. The database must already exist.
 - **username** (*Optional*): The username of the database user.
 - **password** (*Optional*): The password for the database user account.
-
+- **ssl** (*Optional*): Use https instead of http to connect. Defaults to false.
+- **verify_ssl** (*Optional*): Verify SSL certificate for https request. Defaults to false.
diff --git a/source/_components/input_select.markdown b/source/_components/input_select.markdown
@@ -0,0 +1,44 @@
+---
+layout: page
+title: "Input Select"
+description: "Instructions how to integrate the Input Select component into Home Assistant."
+date: 2016-02-02 17:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: home-assistant.png
+ha_category: Automation
+---
+
+The `input_select` component allows the user to define a list of values that can be selected via the frontend and can be used within conditions of automation. 
+
+To enable this platform, add the following lines to your `configuration.yaml`:
+
+```yaml
+# Example configuration.yaml entry
+input_select:
+  who_cooks:
+    name: Who cooks today
+    options:
+     - Paulus
+     - Anne Therese
+    initial: Anne Therese
+    icon: mdi:panda
+  living_room_preset:
+    options:
+      - Visitors
+      - Visitors with kids
+      - Home Alone
+```
+
+Configuration variables:
+
+- **[alias]** (*Required*): Alias for the input.
+- **name** (*Optional*): Friendly name of the input.
+- **options** array (*Optional*): List of options to choose from
+- **initial** (*Optional*): Initial value when Home Assistant starts.
+- **icon** (*Optional*): Icon for entry.
+
+Pick an icon that you can find on [materialdesignicons.com](https://materialdesignicons.com/) to use for your input and prefix the name with `mdi:`. For example `mdi:car`, `mdi:ambulance`, or  `mdi:motorbike`.
+
diff --git a/source/_components/light.scsgate.markdown b/source/_components/light.scsgate.markdown
@@ -0,0 +1,29 @@
+---
+layout: page
+title: "SCSGate light"
+description: "Instructions how to integrate SCSGate lights into Home Assistant."
+date: 2016-01-31 19:30
+sidebar: true
+comments: false
+sharing: true
+footer: true
+ha_category: Light
+---
+
+The SCSGate device can control lights of the BTicino MyHome system.
+
+To enable SCSGate lights in your installation, add the following to your `configuration.yaml` file:
+
+```yaml
+# Example configuration.yaml entry
+light:
+  platform: scsgate
+  devices:
+    living_room:
+      name: Living Room
+      scs_id: XXXXX
+```
+
+Configuration variables:
+
+- **devices** (*Required*): A list of devices with their name to use in the frontend.
diff --git a/source/_components/lock.verisure.markdown b/source/_components/lock.verisure.markdown
@@ -0,0 +1,18 @@
+---
+layout: page
+title: "Verisure Lock"
+description: "Instructions how to setup the Verisure locks within Home Assistant."
+date: 2016-02-12 06:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: wink.png
+ha_category: Lock
+---
+
+
+The Verisure lock platform allows you to control your [Verisure](https://www.verisure.com/) locks.
+
+The requirement is that you have setup your [Verisure hub](/components/verisure/).
+
diff --git a/source/_components/media_player.kodi.markdown b/source/_components/media_player.kodi.markdown
@@ -21,15 +21,17 @@ To add Kodi to your installation, add the following to your `configuration.yaml`
 # Example configuration.yaml entry
 media_player:
   platform: kodi
-  url: http://192.168.0.123/jsonrpc
+  host: 192.168.0.123
+  port: 8080
   name: Kodi
   user: USERNAME
   password: PASSWORD
 ```
 
 Configuration variables:
 
-- **url** *Required*: The URL of the XBMC/Kodi JSON-RPC API, eg. http://192.168.0.123/jsonrpc
+- **host** *Required*: The host name or address of the device that is running XBMC/Kodi
+- **port** *Required*: The port number, default 8080
 - **name** *Optional*: The name of the device used in the frontend.
 - **username** *Optional*: The XBMC/Kodi HTTP username.
 - **password** *Optional*: The XBMC/Kodi HTTP password.
diff --git a/source/_components/media_player.samsungtv.markdown b/source/_components/media_player.samsungtv.markdown
@@ -0,0 +1,25 @@
+---
+layout: page
+title: "Samsung TV"
+description: "Instructions how to integrate a Samsung TV in Home Assistant."
+date: 2016-02-01 19:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: samsung.png
+ha_category: Media Player
+featured: false
+---
+
+The `samsungtv` platform allows you to control an [Samsung TV](http://www.samsung.com).
+
+
+To add an Samsung TV to your installation, add the following to your `configuration.yaml` file:
+
+```yaml
+# Example configuration.yaml entry
+media_player:
+  platform: samsungtv
+```
+
diff --git a/source/_components/mqtt_eventstream.markdown b/source/_components/mqtt_eventstream.markdown
@@ -8,7 +8,7 @@ comments: false
 sharing: true
 footer: true
 logo: mqtt.png
-ha_category: Others
+ha_category: Other
 ---
 
 The `mqtt_eventstream` components two Home Assistant instances via MQTT.

diff --git a/source/_components/mysensors.markdown b/source/_components/mysensors.markdown
@@ -24,8 +24,10 @@ mysensors:
   gateways:
     - port: '/dev/ttyUSB0'
       persistence_file: 'path/mysensors.json'
+      baud_rate: 38400
     - port: '/dev/ttyACM1'
       persistence_file: 'path/mysensors2.json'
+      baud_rate: 115200
   debug: true
   persistence: true
   version: '1.5'
@@ -38,6 +40,7 @@ Configuration variables:
 - **persistence** (*Optional*): Enable or disable local persistence of sensor information. If this is disabled, then each sensor will need to send presentation messages after Home Assistant starts. Default is true.
 - **persistence_file** (*Optional*): Path to a file to save sensor information. The file extension determines the file type. Currently supported file types are 'pickle' and 'json'.
 - **version** (*Optional*): Specifies the MySensors protocol version to use. Supports 1.4 and 1.5. Default is 1.4.
+- **baud_rate** (*Optional*): Specifies baud rate of the connected gateway.
 
 If you are using an original Arduino the port will be named `ttyACM*`. The exact number can be determined with the command shown below.