jeena/home-assistant.github.io
1
0
Fork 0
Code Issues Pull requests Projects Packages Wiki Activity Actions

Convert subpages to folders

Browse source
This commit is contained in:
Paulus Schoutsen 2015-10-26 23:24:55 -07:00
parent aaa837c3e7
commit e59252a39b
81 changed files with 184 additions and 184 deletions
Download patch file Download diff file Expand all files Collapse all files

6
source/_components/alarm_control_panel.markdown
View file

@ -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/)

4
source/_components/arduino.markdown
View file

@ -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/)

10
source/_components/automation.markdown
View file

@ -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 %}

2
source/_components/device_sun_light_trigger.markdown
View file

@ -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:

2
source/_components/device_tracker.actiontec.markdown
View file

@ -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.

2
source/_components/device_tracker.aruba.markdown
View file

@ -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.

2
source/_components/device_tracker.asuswrt.markdown
View file

@ -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.

2
source/_components/device_tracker.ddwrt.markdown
View file

@ -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.

4
source/_components/device_tracker.luci.markdown
View file

@ -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.

2
source/_components/device_tracker.markdown
View file

@ -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):

2
source/_components/device_tracker.netgear.markdown
View file

@ -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.

2
source/_components/device_tracker.nmap_scanner.markdown
View file

@ -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.

4
source/_components/device_tracker.owntracks.markdown
View file

@ -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:

2
source/_components/device_tracker.snmp.markdown
View file

@ -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.

2
source/_components/device_tracker.thomson.markdown
View file

@ -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.

2
source/_components/device_tracker.tomato.markdown
View file

@ -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.

2
source/_components/device_tracker.tplink.markdown
View file

@ -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.

4
source/_components/device_tracker.ubus.markdown
View file

@ -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.

2
source/_components/discovery.markdown
View file

@ -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.

2
source/_components/ifttt.manything.markdown
View file

@ -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.

2
source/_components/ifttt.markdown
View file

@ -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.

2
source/_components/light.hue.markdown
View file

@ -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`:

4
source/_components/light.markdown
View file

@ -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 |
| ---------------------- | -------- | ----------- |

2
source/_components/light.wink.markdown
View file

@ -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/).

2
source/_components/media_player.cast.markdown
View file

@ -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`:

2
source/_components/media_player.plex.markdown
View file

@ -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>.

4
source/_components/modbus.markdown
View file

@ -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/)

14
source/_components/mqtt.markdown
View file

@ -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 %}

2
source/_components/notify.file.markdown
View file

@ -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/).

2
source/_components/notify.instapush.markdown
View file

@ -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/).

2
source/_components/notify.markdown
View file

@ -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/).

2
source/_components/notify.nma.markdown
View file

@ -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/).

2
source/_components/notify.pushbullet.markdown
View file

@ -30,4 +30,4 @@ Configuration variables:
- **name** (*Optional*): Setting the optional parameter `name` allows multiple notifiers to be created. The default value is `notify`. The notifier will bind to the service `notify.NOTIFIER_NAME`.
- **api_key** (*Required*): Enter the API key for PushBullet. Go to https://www.pushbullet.com/ to retrieve your API key.
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/).

2
source/_components/notify.pushover.markdown
View file

@ -36,5 +36,5 @@ This is a quote from the pushover website regarding free/open source apps:
When setting up the application you can use this [icon](https://home-assistant.io/images/favicon-192x192.png).
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/).

2
source/_components/notify.slack.markdown
View file

@ -33,5 +33,5 @@ Configuration variables:
- **api_key** (*Required*): The slack API token to use for sending slack messages. You can get your slack API token here https://api.slack.com/web?sudo=1
- **default_channel** (*Required*): The default channel to post to if no channel is explicitly specified when sending the notification message.
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/).

2
source/_components/notify.smtp.markdown
View file

@ -51,4 +51,4 @@ Keep in mind that if the password contains a colon, it needs to be wrapped in ap
For Google Mail (smtp.gmail.com) an additional step in the setup process is needed. Google has some extra layers of protection
which need special attention. By default, the usage by external applications, especially scripts, is limited. Visit the [Less secure apps](https://www.google.com/settings/security/lesssecureapps) page and enable it.
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/).

2
source/_components/notify.syslog.markdown
View file

@ -57,4 +57,4 @@ The table contains values to use in your `configuration.yaml` file.
For details about facility, option, and priority please consult the [wikpedia article](http://en.wikipedia.org/wiki/Syslog) and [RFC 3164](http://tools.ietf.org/html/rfc3164).
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/).

2
source/_components/notify.telegram.markdown
View file

@ -48,4 +48,4 @@ The default value is `notify`. The notifier will bind to the service
- **api_key** (*Required*): The API token of your bot.
- **chat_id** (*Required*: The chat ID of your user.
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/).

2
source/_components/notify.xmpp.markdown
View file

@ -34,4 +34,4 @@ Configuration variables:
All Jabber IDs (JID) must include the domain. Make sure that the password matches the account provided as sender.
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/).

2
source/_components/sensor.command_sensor.markdown
View file

@ -75,7 +75,7 @@ The `correction_factor` will make sure that the value is shown in a useful forma
### {% linkable_title Use an external script %}
The example is doing the same as the [aREST sensor](/components/sensor.arest.html) but with an external Python script. It should give you an idea about interacting with devices which are exposing a RESTful API.
The example is doing the same as the [aREST sensor](/components/sensor.arest/) but with an external Python script. It should give you an idea about interacting with devices which are exposing a RESTful API.
The one-line script to retrieve a value is shown below. Of course would it be possible to use this directly in the `configuration.yaml` file but need extra care about the quotation marks.

2
source/_components/sensor.rest.markdown
View file

@ -86,7 +86,7 @@ To display the IP address, the entry for a sensor in the `configuration.yaml` fi
### {% linkable_title Single value from a local Glances instance %}
The [glances](/components/sensor.glances.html) sensor is doing the exact same thing for all exposed values.
The [glances](/components/sensor.glances/) sensor is doing the exact same thing for all exposed values.
Add something similar to the entry below to your `configuration.yaml` file:

2
source/_components/sensor.wink.markdown
View file

@ -14,5 +14,5 @@ ha_category: Sensor
The wink sensor platform allows you to get data from your [Wink](http://www.wink.com/) sensors.
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/).

4
source/_components/simple_alarm.markdown
View file

@ -11,9 +11,9 @@ ha_category: Alarm
---
The component `simple_alarm` is capable of detecting intruders. It does so by checking if lights are being turned on while there is no one at home. When this happens it will turn the lights red, flash them for 30 seconds and send a message via [the notifiy component]({{site_root}}/components/notify.html). It will also flash a specific light when a known person comes home.
The component `simple_alarm` is capable of detecting intruders. It does so by checking if lights are being turned on while there is no one at home. When this happens it will turn the lights red, flash them for 30 seconds and send a message via [the notifiy component]({{site_root}}/components/notify/). It will also flash a specific light when a known person comes home.
This component depends on the components [device_tracker]({{site_root}}/components/device_tracker.html) and [light]({{site_root}}/components/light.html) being setup.
This component depends on the components [device_tracker]({{site_root}}/components/device_tracker/) and [light]({{site_root}}/components/light/) being setup.
To set it up, add the following lines to your `configuration.yaml` file:

2
source/_components/sun.markdown
View file

@ -14,7 +14,7 @@ ha_category: Weather
The `sun` component will use your current location to track if the sun is above or below the horizon.
The sun can be used within automation as [a trigger with an optional offset to simulate dawn/dusk][automation-trigger].
[automation-trigger]: /components/automation.html#sun-trigger
[automation-trigger]: /components/automation/#sun-trigger
```yaml
# Example configuration.yaml entry

2
source/_components/switch.command_switch.markdown
View file

@ -38,7 +38,7 @@ In this section you find some real life examples of how to use this switch.
### {% linkable_title aREST device %}
The example below is doing the same as the [aREST switch](/components/switch.arest.html). The commandline tool `[curl](http://curl.haxx.se/)` is used to toogle a pin which is controllable through REST.
The example below is doing the same as the [aREST switch](/components/switch.arest/). The commandline tool `[curl](http://curl.haxx.se/)` is used to toogle a pin which is controllable through REST.
```yaml
# Example configuration.yaml entry

2
source/_components/switch.wink.markdown
View file

@ -14,5 +14,5 @@ ha_category: Switch
The wink switch platform allows you to control your [Wink](http://www.wink.com/) switches.
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/).

6
source/_components/vera.markdown
View file

@ -16,6 +16,6 @@ The [Vera](http://getvera.com) ecosystem is using Z-Wave for communication betwe
## {% linkable_title Building on top of Vera %}
- [Vera Sensor](/components/sensor.vera.html)
- [Vera Switch](/components/switch.vera.html)
- [Vera Light](/components/light.vera.html)
- [Vera Sensor](/components/sensor.vera/)
- [Vera Switch](/components/switch.vera/)
- [Vera Light](/components/light.vera/)

2
source/_components/zone.markdown
View file

@ -12,7 +12,7 @@ ha_category: Organization
Zones allow you to specify certain regions on earth (for now). When a device tracker sees a device
to be within a zone, the state will take the name from the zone. Zones can also be used as a
[trigger](/components/automation.html#zone-trigger) or [condition](/components/automation.html#zone-condition)
[trigger](/components/automation/#zone-trigger) or [condition](/components/automation/#zone-condition)
inside automation setups.
Zones support the usual method to specify multiple zones, use keys `zone:`, `zone 2:` etc.