Convert subpages to folders

sts098 · Oct 27, 2015 · e59252a · e59252a
1 parent aaa837c
commit e59252a
Show file tree

Hide file tree

Showing 81 changed files with 184 additions and 184 deletions.
diff --git a/source/_components/alarm_control_panel.markdown b/source/_components/alarm_control_panel.markdown
@@ -12,7 +12,7 @@ footer: true
 
 Home Assistant can give you an interface with is similar to a classic alarm system. There are several panels supported:
 
-- [Manual](/components/alarm_control_panel.manual.html)
-- [MQTT](/components/alarm_control_panel.mqtt.html)
-- [Verisure](/components/verisure.html)
+- [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
@@ -46,6 +46,6 @@ A word of caution: The Arduino boards are not storing states. This means that wi
 
 ## Building on top of the Arduino component
 
- - [Arduino Sensor](/components/sensor.arduino.html)
- - [Arduino Switch](/components/switch.arduino.html)
+ - [Arduino Sensor](/components/sensor.arduino/)
+ - [Arduino Switch](/components/switch.arduino/)
 
diff --git a/source/_components/automation.markdown b/source/_components/automation.markdown
@@ -11,7 +11,7 @@ ha_category: Automation
 ---
 
 This page will go into more detail about the various options the `automation` component offers. If
-you haven't yet, read the [getting started page on automation](/getting-started/automation.html).
+you haven't yet, read the [getting started page on automation](/getting-started/automation/).
 
 A configuration section of an automation requires a `trigger` and an `action` section. `condition` and
 `condition_type` are optional. To keep this page compact, all following sections will not show the
@@ -185,7 +185,7 @@ The above example will trigger on Saturday and Sunday every hour on the 5 (2:05,
 #### {% linkable_title Zone trigger %}
 Zone triggers can trigger when an entity is entering or leaving the zone. For zone automation to work,
 you need to have setup a device tracker platform that supports reporting GPS coordinates. Currently
-this is limited to the [OwnTracks platform](/components/device_tracker.owntracks.html).
+this is limited to the [OwnTracks platform](/components/device_tracker.owntracks/).
 
 ```yaml
 automation:
@@ -273,7 +273,7 @@ Valid values for `weekday` are (sun, mon, tue, wed, thu, fri & sat)
 #### {% linkable_title Zone condition %}
 Zone conditions test if an entity is in a certain zone. For zone automation to work,
 you need to have setup a device tracker platform that supports reporting GPS coordinates. Currently
-this is limited to the [OwnTracks platform](/components/device_tracker.owntracks.html).
+this is limited to the [OwnTracks platform](/components/device_tracker.owntracks/).
 
 ```yaml
 automation:
@@ -311,8 +311,8 @@ automation:
 ```
 
 If you want to specify multiple services to be called or include a delay, have a look at the
-[script component](/components/script.html). If you want to describe how certain entities should look,
-check out the [scene component](/components/scene.html).
+[script component](/components/script/). If you want to describe how certain entities should look,
+check out the [scene component](/components/scene/).
 
 ## {% linkable_title Troubleshooting %}
 

diff --git a/source/_components/device_sun_light_trigger.markdown b/source/_components/device_sun_light_trigger.markdown
@@ -16,7 +16,7 @@ Home Assistant has a built-in component called `device_sun_light_trigger` to hel
  * Turn on the lights when people get home after the sun has set
  * Turn off the lights when all people leave the house
 
-This component requires the components [sun](/components/sun.html), [device_tracker](/components/device_tracker.html) and [light](/components/light.html) to be enabled.
+This component requires the components [sun](/components/sun/), [device_tracker](/components/device_tracker/) and [light](/components/light/) to be enabled.
 
 To enable this component, add the following lines to your `configuration.yaml` file:
 

diff --git a/source/_components/device_tracker.actiontec.markdown b/source/_components/device_tracker.actiontec.markdown
@@ -39,5 +39,5 @@ Configuration variables:
 - **password** (*Required*): The password for your given admin account.
 - **home_interval** (*Optional*): If the home_interval is set then the component will not let a device be AWAY if it has been HOME in the last home_interval minutes. This is in addition to the 3 minute wait built into the device_tracker component.
 
-See the [device tracker component page](/components/device_tracker.html) for instructions how to configure the people to be tracked.
+See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked.
 
diff --git a/source/_components/device_tracker.aruba.markdown b/source/_components/device_tracker.aruba.markdown
@@ -37,5 +37,5 @@ Configuration variables:
 - **username** *Required*: The username of an user with administrative privileges, usually *admin*.
 - **password** *Required*: The password for your given admin account.
 
-See the [device tracker component page](/components/device_tracker.html) for instructions how to configure the people to be tracked.
+See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked.
 
diff --git a/source/_components/device_tracker.asuswrt.markdown b/source/_components/device_tracker.asuswrt.markdown
@@ -35,4 +35,4 @@ Configuration variables:
 - **username** (*Required*: The username of an user with administrative privileges, usually *admin*.
 - **password** (*Required*): The password for your given admin account.
 
-See the [device tracker component page](/components/device_tracker.html) for instructions how to configure the people to be tracked.
+See the [device tracker component page](/components/device_tracker/) 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
@@ -31,4 +31,4 @@ Configuration variables:
 - **username** (*Required*: The username of an user with administrative privileges, usually *admin*.
 - **password** (*Required*): The password for your given admin account.
 
-See the [device tracker component page](/components/device_tracker.html) for instructions how to configure the people to be tracked.
+See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked.
diff --git a/source/_components/device_tracker.luci.markdown b/source/_components/device_tracker.luci.markdown
@@ -11,7 +11,7 @@ logo: openwrt.png
 ha_category: Presence Detection
 ---
 
-_This is one of the two ways we support OpenWRT. If you encounter problems, try [ubus](/components/device_tracker.ubus.html)._
+_This is one of the two ways we support OpenWRT. If you encounter problems, try [ubus](/components/device_tracker.ubus/)._
 
 This is a presence detection scanner for OpenWRT using [luci](http://wiki.openwrt.org/doc/techref/luci).
 
@@ -36,4 +36,4 @@ Configuration variables:
 - **username** (*Required*): The username of an user with administrative privileges, usually *admin*.
 - **password** (*Required*): The password for your given admin account.
 
-See the [device tracker component page](/components/device_tracker.html) for instructions how to configure the people to be tracked.
+See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked.
diff --git a/source/_components/device_tracker.markdown b/source/_components/device_tracker.markdown
@@ -11,7 +11,7 @@ footer: true
 
 Home Assistant can get information from your wireless router to track which devices are connected. Please check the sidebar for a list of  brands of supported wireless routers.
 
-There are also trackers available which uses different technologies like [MQTT](/components/mqtt.html) or [nmap](/components/device_tracker.nmap_scanner.html) to scan the network for devices
+There are also trackers available which uses different technologies like [MQTT](/components/mqtt/) or [nmap](/components/device_tracker.nmap_scanner/) to scan the network for devices
 
 To get started add the following lines to your `configuration.yaml` (example for Netgear):
 

diff --git a/source/_components/device_tracker.netgear.markdown b/source/_components/device_tracker.netgear.markdown
@@ -29,4 +29,4 @@ Configuration variables:
 - **username** (*Required*: The username of an user with administrative privileges, usually *admin*.
 - **password** (*Required*): The password for your given admin account.
 
-See the [device tracker component page](/components/device_tracker.html) for instructions how to configure the people to be tracked.
+See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked.
diff --git a/source/_components/device_tracker.nmap_scanner.markdown b/source/_components/device_tracker.nmap_scanner.markdown
@@ -30,5 +30,5 @@ device_tracker:
 `home_interval` is an optional value set in minutes.  This will be the number of minutes nmap will not
 scan this device, assuming it is home, in order to preserve the device battery.
 
-See the [device tracker component page](/components/device_tracker.html) for instructions how to
+See the [device tracker component page](/components/device_tracker/) for instructions how to
 configure the people to be tracked.
diff --git a/source/_components/device_tracker.owntracks.markdown b/source/_components/device_tracker.owntracks.markdown
@@ -17,8 +17,8 @@ This platform allows you to detect presence using [Owntracks](http://owntracks.o
 users to track their location on Android and iOS phones and publish it to an MQTT broker. This platform
 will connect to the broker and monitor for new locations.
 
-This component requires [the MQTT component](/components/mqtt.html) to be set up and works very well
-together with [the zone component](/components/zone.html).
+This component requires [the MQTT component](/components/mqtt/) to be set up and works very well
+together with [the zone component](/components/zone/).
 
 To integrate Owntracks in Home Assistant, add the following section to your `configuration.yaml` file:
 

diff --git a/source/_components/device_tracker.snmp.markdown b/source/_components/device_tracker.snmp.markdown
@@ -39,4 +39,4 @@ Configuration variables:
 
 - **baseoid** (*Required*): The OID prefix where wireless client registrations can be found, usually vendor specific. It's advised to use the numerical notation. To find this base OID, check vendor documentation or check the MIB file for your device.
 
-See the [device tracker component page](/components/device_tracker.html) for instructions how to configure the people to be tracked.
+See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked.
diff --git a/source/_components/device_tracker.thomson.markdown b/source/_components/device_tracker.thomson.markdown
@@ -31,4 +31,4 @@ Configuration variables:
 - **username** (*Required*: The username of an user with administrative privileges, usually *admin*.
 - **password** (*Required*): The password for your given admin account.
 
-See the [device tracker component page](/components/device_tracker.html) for instructions how to configure the people to be tracked.
+See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked.
diff --git a/source/_components/device_tracker.tomato.markdown b/source/_components/device_tracker.tomato.markdown
@@ -30,4 +30,4 @@ Configuration variables:
 - **password** (*Required*): The password for your given admin account.
 - **http_id** (*Required*): The value can be obtained by logging in to the Tomato admin interface and search for `http_id` in the page source code.
 
-See the [device tracker component page](/components/device_tracker.html) for instructions how to configure the people to be tracked.
+See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked.
diff --git a/source/_components/device_tracker.tplink.markdown b/source/_components/device_tracker.tplink.markdown
@@ -38,4 +38,4 @@ For Archer C9 models running firmware version 150811 or later please use the enc
 5. Type ```document.getElementById("login-password").value;```.
 6. Copy the returned value to your Home Assistant configuration as password.
 
-See the [device tracker component page](/components/device_tracker.html) for instructions how to configure the people to be tracked.
+See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked.
diff --git a/source/_components/device_tracker.ubus.markdown b/source/_components/device_tracker.ubus.markdown
@@ -11,7 +11,7 @@ logo: openwrt.png
 ha_category: Presence Detection
 ---
 
-_This is one of the two ways we support OpenWRT. If you encounter problems, try [luci](/components/device_tracker.luci.html)._
+_This is one of the two ways we support OpenWRT. If you encounter problems, try [luci](/components/device_tracker.luci/)._
 
 This is a presence detection scanner for OpenWRT using [ubus](http://wiki.openwrt.org/doc/techref/ubus).
 
@@ -55,4 +55,4 @@ Configuration variables:
 - **username** (*Required*): The username of an user with administrative privileges, usually *admin*.
 - **password** (*Required*): The password for your given admin account.
 
-See the [device tracker component page](/components/device_tracker.html) for instructions how to configure the people to be tracked.
+See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked.
diff --git a/source/_components/discovery.markdown b/source/_components/discovery.markdown
@@ -28,7 +28,7 @@ To load this component, add the following lines to your `configuration.yaml`:
 discovery:
 ```
 
-If you are developing a new platform, please read [how to make your platform discoverable]({{site_root}}/developers/add_new_platform.html#discovery).
+If you are developing a new platform, please read [how to make your platform discoverable]({{site_root}}/developers/add_new_platform/#discovery).
 
 <p class='note warning'>
 There is currently a <a href='https://bitbucket.org/al45tair/netifaces/issues/17/dll-fails-to-load-windows-81-64bit'>known issue</a> with running this playform on a 64-bit version of Python.

diff --git a/source/_components/ifttt.manything.markdown b/source/_components/ifttt.manything.markdown
@@ -15,7 +15,7 @@ ha_category: Camera
 camera for monitoring your home, your pets, anything! Comes with live streaming, motion activated alerts, cloud video recording, and more.
 
 To get manything support, HA will use IFTTT's [Maker Channel](https://ifttt.com/maker) and the [ManyThing Channel](https://ifttt.com/manything).
-Use the [IFTTT Setup instructions](/components/ifttt.html) to activate the IFTTT Platform.
+Use the [IFTTT Setup instructions](/components/ifttt/) to activate the IFTTT Platform.
 
 After setting up IFTTT, Maker Channel and ManyThing Channel, you can use the following examples to configure Home Assistant.
 

diff --git a/source/_components/ifttt.markdown b/source/_components/ifttt.markdown
@@ -76,4 +76,4 @@ Additional examples of using IFTTT channels can be found below.
 
 Channel | Description
 ----- | -----
-[Manything](/components/ifttt.manything.html) | Automates turning recording ON and OFF based on Home Assistant AWAY and HOME values.
+[Manything](/components/ifttt.manything/) | Automates turning recording ON and OFF based on Home Assistant AWAY and HOME values.
diff --git a/source/_components/light.hue.markdown b/source/_components/light.hue.markdown
@@ -14,7 +14,7 @@ featured: true
 
 
 
-Philips Hue support is integrated into Home Assistant as a light platform. The preferred way to setup the Philips Hue platform is by enabling the [the discovery component]({{site_root}}/components/discovery.html).
+Philips Hue support is integrated into Home Assistant as a light platform. The preferred way to setup the Philips Hue platform is by enabling the [the discovery component]({{site_root}}/components/discovery/).
 
 If you want to enable the light component directly, add the following lines to your `configuration.yaml`:
 

diff --git a/source/_components/light.markdown b/source/_components/light.markdown
@@ -18,7 +18,7 @@ It supports the following platforms:
  * `hue` for Philips Hue
  * `wink` for Wink
 
-Preferred way to setup the Philips Hue platform is through the [the discovery component]({{site_root}}/components/discovery.html). For the Wink light platform enable [the wink component]({{site_root}}/components/wink.html).
+Preferred way to setup the Philips Hue platform is through the [the discovery component]({{site_root}}/components/discovery/). For the Wink light platform enable [the wink component]({{site_root}}/components/wink/).
 
 If you want to enable the light component directly, add the following lines to your `configuration.yaml`:
 
@@ -33,7 +33,7 @@ The light component supports multiple entries in <code>configuration.yaml</code>
 
 ### Service `light.turn_on`
 
-Turns one light on or multiple lights on using [groups]({{site_root}}/components/group.html).
+Turns one light on or multiple lights on using [groups]({{site_root}}/components/group/).
 
 | Service data attribute | Optional | Description |
 | ---------------------- | -------- | ----------- |

diff --git a/source/_components/light.wink.markdown b/source/_components/light.wink.markdown
@@ -14,4 +14,4 @@ ha_category: Light
 
 The wink sensor 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.html).
+The requirement is that you have setup your [Wink hub](/components/light.wink/).
diff --git a/source/_components/media_player.cast.markdown b/source/_components/media_player.cast.markdown
@@ -13,7 +13,7 @@ featured: true
 ---
 
 
-Google Cast devices will be automatically discovered if you enable [the discovery component]({{site_root}}/components/discovery.html). There is a issue where Chromecasts can only be discovered if your device is connected to the same subnet as your Chromecast.
+Google Cast devices will be automatically discovered if you enable [the discovery component]({{site_root}}/components/discovery/). There is a issue where Chromecasts can only be discovered if your device is connected to the same subnet as your Chromecast.
 
 Chromecast platform can also be forced to load by adding the following lines to your `configuration.yaml`:
 

diff --git a/source/_components/media_player.plex.markdown b/source/_components/media_player.plex.markdown
@@ -14,7 +14,7 @@ featured: true
 
 
 The Plex platform allows you to connect a [Plex Media Server](https://plex.tv) to Home Assistant. It will allow you to control media playback and see the current playing item.
-The preferred way to setup the Plex platform is by enabling the the [the discovery component]({{site_root}}/components/discovery.html) and requires GDM to be enabled.
+The preferred way to setup the Plex platform is by enabling the the [the discovery component]({{site_root}}/components/discovery/) and requires GDM to be enabled.
 
 If local authentication is enabled or multiple users are defined, HASS requires an authentication token to be entered in the webinterface. See <A TARGET="_new" HREF=https://support.plex.tv/hc/en-us/articles/204059436>Finding your account token / X-Plex-Token</A>.
 

diff --git a/source/_components/modbus.markdown b/source/_components/modbus.markdown
@@ -57,6 +57,6 @@ Configuration variables:
 
 ## {% linkable_title Building on top of Modbus %}
 
- - [Modbus Sensor](/components/sensor.modbus.html)
- - [Modbus Switch](/components/switch.modbus.html)
+ - [Modbus Sensor](/components/sensor.modbus/)
+ - [Modbus Switch](/components/switch.modbus/)
 
diff --git a/source/_components/mqtt.markdown b/source/_components/mqtt.markdown
@@ -82,7 +82,7 @@ mqtt:
 
 [CloudMQTT](https://www.cloudmqtt.com) is a hosted private MQTT instance that is free up to 10
 connected devices. This is enough to get started with for example
-[OwnTracks](/components/device_tracker.owntracks.html) and give you a taste of what is possible.
+[OwnTracks](/components/device_tracker.owntracks/) and give you a taste of what is possible.
 
 <p class='note'>
 Home Assistant is not affiliated with CloudMQTT nor will receive any kickbacks.
@@ -112,12 +112,12 @@ of CloudMQTT (port range 20 000 - 30 000).
 
 ## {% linkable_title Building on top of MQTT %}
 
- - [MQTT Sensor](/components/sensor.mqtt.html)
- - [MQTT Switch](/components/switch.mqtt.html)
- - [MQTT Device Tracker](/components/device_tracker.mqtt.html)
- - [OwnTracks Device Tracker](/components/device_tracker.owntracks.html)
- - [MQTT automation rule](/components/automation.html#mqtt-based-automation)
- - [MQTT alarm](/components/alarm_control_panel.mqtt.html)
+ - [MQTT Sensor](/components/sensor.mqtt/)
+ - [MQTT Switch](/components/switch.mqtt/)
+ - [MQTT Device Tracker](/components/device_tracker.mqtt/)
+ - [OwnTracks Device Tracker](/components/device_tracker.owntracks/)
+ - [MQTT automation rule](/components/automation/#mqtt-based-automation)
+ - [MQTT alarm](/components/alarm_control_panel.mqtt/)
  - 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.
 
 ## {% linkable_title Testing your setup %}

diff --git a/source/_components/notify.file.markdown b/source/_components/notify.file.markdown
@@ -30,4 +30,4 @@ Configuration variables:
 - **filename** (*Required*): Name of the file to use. The file will be created if it doesn't exist and saved in your `config/` folder.
 - **timestamp** (*Optional*): Setting `timestamp` to 1 adds a timestamp to every entry.
 
-To use notifications, please see the [getting started with automation page]({{site_root}}/components/automation.html).
+To use notifications, please see the [getting started with automation page]({{site_root}}/components/automation/).
diff --git a/source/_components/notify.instapush.markdown b/source/_components/notify.instapush.markdown
@@ -49,4 +49,4 @@ curl -X POST \
 ```
 For further details, please check the [API](https://instapush.im/developer/rest).
 
-To use notifications, please see the [getting started with automation page]({{site_root}}/components/automation.html).
+To use notifications, please see the [getting started with automation page]({{site_root}}/components/automation/).
diff --git a/source/_components/notify.markdown b/source/_components/notify.markdown
@@ -40,4 +40,4 @@ automation:
   service_data: {"message":"YAY"}
 ```
 
-For more automation examples, see the [getting started with automation page]({{site_root}}/components/automation.html).
+For more automation examples, see the [getting started with automation page]({{site_root}}/components/automation/).
diff --git a/source/_components/notify.nma.markdown b/source/_components/notify.nma.markdown
@@ -31,4 +31,4 @@ Configuration variables:
 
 Details for the API : https://www.notifymyandroid.com/api.jsp
 
-To use notifications, please see the [getting started with automation page]({{site_root}}/components/automation.html).
+To use notifications, please see the [getting started with automation page]({{site_root}}/components/automation/).
Original file line number	Diff line number	Diff line change
Expand Up		@@ -39,4 +39,4 @@ Configuration variables:

		- baseoid (Required): The OID prefix where wireless client registrations can be found, usually vendor specific. It's advised to use the numerical notation. To find this base OID, check vendor documentation or check the MIB file for your device.

		See the [device tracker component page](/components/device_tracker.html) for instructions how to configure the people to be tracked.
		See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked.
Original file line number	Diff line number	Diff line change
Expand Up		@@ -14,7 +14,7 @@ featured: true



		Philips Hue support is integrated into Home Assistant as a light platform. The preferred way to setup the Philips Hue platform is by enabling the [the discovery component]({{site_root}}/components/discovery.html).
		Philips Hue support is integrated into Home Assistant as a light platform. The preferred way to setup the Philips Hue platform is by enabling the [the discovery component]({{site_root}}/components/discovery/).

		If you want to enable the light component directly, add the following lines to your `configuration.yaml`:

Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -14,4 +14,4 @@ ha_category: Light

		The wink sensor 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.html).
		The requirement is that you have setup your [Wink hub](/components/light.wink/).
-Original file line number
+Diff line change
@@ Expand Up / @@ -13,7 +13,7 @@ featured: true @@
     ---
-    Google Cast devices will be automatically discovered if you enable [the discovery component]({{site_root}}/components/discovery.html). There is a issue where Chromecasts can only be discovered if your device is connected to the same subnet as your Chromecast.
+    Google Cast devices will be automatically discovered if you enable [the discovery component]({{site_root}}/components/discovery/). There is a issue where Chromecasts can only be discovered if your device is connected to the same subnet as your Chromecast.
     Chromecast platform can also be forced to load by adding the following lines to your `configuration.yaml`:
@@ Expand Down @@
Original file line number	Diff line number	Diff line change
Expand Up		@@ -31,4 +31,4 @@ Configuration variables:

		Details for the API : https://www.notifymyandroid.com/api.jsp

		To use notifications, please see the [getting started with automation page]({{site_root}}/components/automation.html).
		To use notifications, please see the [getting started with automation page]({{site_root}}/components/automation/).