jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-18 23:06:58 +00:00
Code Issues Packages Projects Releases Wiki Activity

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
Show Stats 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: 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) - [Manual](/components/alarm_control_panel.manual/)
- [MQTT](/components/alarm_control_panel.mqtt.html) - [MQTT](/components/alarm_control_panel.mqtt/)
- [Verisure](/components/verisure.html) - [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 ## Building on top of the Arduino component
- [Arduino Sensor](/components/sensor.arduino.html) - [Arduino Sensor](/components/sensor.arduino/)
- [Arduino Switch](/components/switch.arduino.html) - [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 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 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 `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 %} #### {% linkable_title Zone trigger %}
Zone triggers can trigger when an entity is entering or leaving the zone. For zone automation to work, 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 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 ```yaml
automation: automation:
@ -273,7 +273,7 @@ Valid values for `weekday` are (sun, mon, tue, wed, thu, fri & sat)
#### {% linkable_title Zone condition %} #### {% linkable_title Zone condition %}
Zone conditions test if an entity is in a certain zone. For zone automation to work, 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 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 ```yaml
automation: 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 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, [script component](/components/script/). If you want to describe how certain entities should look,
check out the [scene component](/components/scene.html). check out the [scene component](/components/scene/).
## {% linkable_title Troubleshooting %} ## {% 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 on the lights when people get home after the sun has set
* Turn off the lights when all people leave the house * 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: 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. - **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. - **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*. - **username** *Required*: The username of an user with administrative privileges, usually *admin*.
- **password** *Required*: The password for your given admin account. - **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*. - **username** (*Required*: The username of an user with administrative privileges, usually *admin*.
- **password** (*Required*): The password for your given admin account. - **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*. - **username** (*Required*: The username of an user with administrative privileges, usually *admin*.
- **password** (*Required*): The password for your given admin account. - **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 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). 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*. - **username** (*Required*): The username of an user with administrative privileges, usually *admin*.
- **password** (*Required*): The password for your given admin account. - **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. 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): 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*. - **username** (*Required*: The username of an user with administrative privileges, usually *admin*.
- **password** (*Required*): The password for your given admin account. - **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 `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. 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. 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 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. 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 This component requires [the MQTT component](/components/mqtt/) to be set up and works very well
together with [the zone component](/components/zone.html). together with [the zone component](/components/zone/).
To integrate Owntracks in Home Assistant, add the following section to your `configuration.yaml` file: 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. - **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*. - **username** (*Required*: The username of an user with administrative privileges, usually *admin*.
- **password** (*Required*): The password for your given admin account. - **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. - **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. - **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;```. 5. Type ```document.getElementById("login-password").value;```.
6. Copy the returned value to your Home Assistant configuration as password. 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 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). 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*. - **username** (*Required*): The username of an user with administrative privileges, usually *admin*.
- **password** (*Required*): The password for your given admin account. - **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: 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'> <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. 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. 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). 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. 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 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`: 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 * `hue` for Philips Hue
* `wink` for Wink * `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`: 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` ### 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 | | 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 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`: 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 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>. 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 %} ## {% linkable_title Building on top of Modbus %}
- [Modbus Sensor](/components/sensor.modbus.html) - [Modbus Sensor](/components/sensor.modbus/)
- [Modbus Switch](/components/switch.modbus.html) - [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 [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 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'> <p class='note'>
Home Assistant is not affiliated with CloudMQTT nor will receive any kickbacks. 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 %} ## {% linkable_title Building on top of MQTT %}
- [MQTT Sensor](/components/sensor.mqtt.html) - [MQTT Sensor](/components/sensor.mqtt/)
- [MQTT Switch](/components/switch.mqtt.html) - [MQTT Switch](/components/switch.mqtt/)
- [MQTT Device Tracker](/components/device_tracker.mqtt.html) - [MQTT Device Tracker](/components/device_tracker.mqtt/)
- [OwnTracks Device Tracker](/components/device_tracker.owntracks.html) - [OwnTracks Device Tracker](/components/device_tracker.owntracks/)
- [MQTT automation rule](/components/automation.html#mqtt-based-automation) - [MQTT automation rule](/components/automation/#mqtt-based-automation)
- [MQTT alarm](/components/alarm_control_panel.mqtt.html) - [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. - 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 %} ## {% 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. - **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. - **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). 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"} 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 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`. - **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. - **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). 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 - **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. - **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 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. 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). 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. - **api_key** (*Required*): The API token of your bot.
- **chat_id** (*Required*: The chat ID of your user. - **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. 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 %} ### {% 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. 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 %} ### {% 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: 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 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: 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` 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]. 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 ```yaml
# Example configuration.yaml entry # 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 %} ### {% 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 ```yaml
# Example configuration.yaml entry # 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 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 %} ## {% linkable_title Building on top of Vera %}
- [Vera Sensor](/components/sensor.vera.html) - [Vera Sensor](/components/sensor.vera/)
- [Vera Switch](/components/switch.vera.html) - [Vera Switch](/components/switch.vera/)
- [Vera Light](/components/light.vera.html) - [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 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 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. inside automation setups.
Zones support the usual method to specify multiple zones, use keys `zone:`, `zone 2:` etc. Zones support the usual method to specify multiple zones, use keys `zone:`, `zone 2:` etc.

2
source/_cookbook/automation_for_rainy_days.markdown
View File

@ -11,7 +11,7 @@ footer: true
### Rainy Day Light ### ### Rainy Day Light ###
This requires a [forecast.io](components/sensor.forecast.html) sensor with the condition `weather_precip` that tells if it's raining or not. This requires a [forecast.io](components/sensor.forecast/) sensor with the condition `weather_precip` that tells if it's raining or not.
Turn on a light in the living room when it starts raining, someone is home, and it's afternoon or later. Turn on a light in the living room when it starts raining, someone is home, and it's afternoon or later.

2
source/_includes/asides/component_navigation.html
View File

@ -11,7 +11,7 @@
{% assign is_platform = true %} {% assign is_platform = true %}
{% assign imp_name = file_parts[1] %} {% assign imp_name = file_parts[1] %}
{% assign parent_name = file_parts[0] %} {% assign parent_name = file_parts[0] %}
{% assign parent_url = parent_name | prepend: '/components/' | append: '.html' %} {% assign parent_url = parent_name | prepend: '/components/' | append: '/' %}
{% assign parent_component = components | where: 'url', parent_url | first %} {% assign parent_component = components | where: 'url', parent_url | first %}
{% else %} {% else %}
{% assign is_platform = false %} {% assign is_platform = false %}

28
source/_includes/custom/grid_item_left.html
View File

@ -2,46 +2,46 @@
<hr> <hr>
<p>Home Assistant will track the state of all the devices in your home, so you don't have to.</p> <p>Home Assistant will track the state of all the devices in your home, so you don't have to.</p>
<div class='supported-brands clearfix'> <div class='supported-brands clearfix'>
<a href='/components/thermostat.nest.html'> <a href='/components/thermostat.nest/'>
<img src='/images/supported_brands/nest_thermostat.png' /> <img src='/images/supported_brands/nest_thermostat.png' />
</a> </a>
<a href='/components/light.hue.html'> <a href='/components/light.hue/'>
<img src='/images/supported_brands/philips_hue.png' /> <img src='/images/supported_brands/philips_hue.png' />
</a> </a>
<a href='/components/mqtt.html'> <a href='/components/mqtt/'>
<img src='/images/supported_brands/mqtt.png' /> <img src='/images/supported_brands/mqtt.png' />
</a> </a>
<a href='/components/media_player.cast.html'> <a href='/components/media_player.cast/'>
<img src='/images/supported_brands/google_cast.png' /> <img src='/images/supported_brands/google_cast.png' />
</a> </a>
<a href='/components/switch.wemo.html'> <a href='/components/switch.wemo/'>
<img src='/images/supported_brands/belkin_wemo.png' /> <img src='/images/supported_brands/belkin_wemo.png' />
</a> </a>
<a href='/components/notify.pushbullet.html'> <a href='/components/notify.pushbullet/'>
<img src='/images/supported_brands/pushbullet.png' /> <img src='/images/supported_brands/pushbullet.png' />
</a> </a>
<a href='/components/ifttt.html'> <a href='/components/ifttt/'>
<img src='/images/supported_brands/ifttt.png' /> <img src='/images/supported_brands/ifttt.png' />
</a> </a>
<a href='/components/wink.html'> <a href='/components/wink/'>
<img src='/images/supported_brands/wink.png' /> <img src='/images/supported_brands/wink.png' />
</a> </a>
<a href='/components/arduino.html'> <a href='/components/arduino/'>
<img src='/images/supported_brands/arduino.png' /> <img src='/images/supported_brands/arduino.png' />
</a> </a>
<a href='/components/device_tracker.netgear.html'> <a href='/components/device_tracker.netgear/'>
<img src='/images/supported_brands/netgear.png' /> <img src='/images/supported_brands/netgear.png' />
</a> </a>
<a href='/components/media_player.kodi.html'> <a href='/components/media_player.kodi/'>
<img src='/images/supported_brands/kodi.png' /> <img src='/images/supported_brands/kodi.png' />
</a> </a>
<a href='/components/media_player.plex.html'> <a href='/components/media_player.plex/'>
<img src='/images/supported_brands/plex.png' /> <img src='/images/supported_brands/plex.png' />
</a> </a>
<a href='/components/device_tracker.luci.html'> <a href='/components/device_tracker.luci/'>
<img src='/images/supported_brands/openwrt.png' /> <img src='/images/supported_brands/openwrt.png' />
</a> </a>
<a href='/components/vera.html'> <a href='/components/vera/'>
<img src='/images/supported_brands/vera.png' /> <img src='/images/supported_brands/vera.png' />
</a> </a>
</div> </div>

20
source/_includes/custom/navigation.html
View File

@ -3,10 +3,10 @@
<a href="{{ root_url }}/getting-started/">Getting started</a> <a href="{{ root_url }}/getting-started/">Getting started</a>
<ul> <ul>
<li><a href='/getting-started/'>Installing Home Assistant</a></li> <li><a href='/getting-started/'>Installing Home Assistant</a></li>
<li><a href='/getting-started/configuration.html'>Configuration basics</a></li> <li><a href='/getting-started/configuration/'>Configuration basics</a></li>
<li><a href='/getting-started/devices.html'>Adding devices</a></li> <li><a href='/getting-started/devices/'>Adding devices</a></li>
<li><a href='/getting-started/presence-detection.html'>Presence detection</a></li> <li><a href='/getting-started/presence-detection/'>Presence detection</a></li>
<li><a href='/getting-started/automation.html'>Automation</a></li> <li><a href='/getting-started/automation/'>Automation</a></li>
<li><a href='/cookbook'>Configuration cookbook</a></li> <li><a href='/cookbook'>Configuration cookbook</a></li>
</ul> </ul>
</li> </li>
@ -14,16 +14,16 @@
<li> <li>
<a href="{{ root_url }}/developers/">Developers</a> <a href="{{ root_url }}/developers/">Developers</a>
<ul> <ul>
<li><a href="{{ root_url }}/developers/architecture.html">Architecture</a></li> <li><a href="{{ root_url }}/developers/architecture/">Architecture</a></li>
<li><a href="{{ root_url}}/developers/frontend.html">Frontend development</a></li> <li><a href="{{ root_url}}/developers/frontend/">Frontend development</a></li>
<li><a href="{{ root_url}}/developers/creating_components.html"> <li><a href="{{ root_url}}/developers/creating_components/">
Creating components Creating components
</a></li> </a></li>
<li><a href="{{ root_url}}/developers/add_new_platform.html"> <li><a href="{{ root_url}}/developers/add_new_platform/">
Adding platform support Adding platform support
</a></li> </a></li>
<li><a href="{{ root_url }}/developers/api.html">API</a></li> <li><a href="{{ root_url }}/developers/api/">API</a></li>
<li><a href="{{ root_url }}/developers/credits.html">Credits</a></li> <li><a href="{{ root_url }}/developers/credits/">Credits</a></li>
</ul> </ul>
</li> </li>
<li><a href="{{ root_url }}/blog/">Blog</a></li> <li><a href="{{ root_url }}/blog/">Blog</a></li>

2
source/_posts/2015-01-11-bootstrapping-your-setup-with-discovery.markdown
View File

@ -20,4 +20,4 @@ To enable the discovery component, add the following to your `home-assistant.con
[discovery] [discovery]
``` ```
A new [discovery section]({{site_root}}/developers/add_new_platform.html#discovery) has been added to the Adding a new platform page with instructions how to make your platform discoverable. A new [discovery section]({{site_root}}/developers/add_new_platform/#discovery) has been added to the Adding a new platform page with instructions how to make your platform discoverable.

2
source/_posts/2015-02-24-streaming-updates.markdown
View File

@ -18,7 +18,7 @@ A new toggle has been added ot the sidebar to turn streaming updates on and off.
Streaming updates has been implemented using the HTML5 `EventSource` tag. Implementation is pretty straight forward as all the reconnection logic will be handled by the event source tag. The [server-side code](https://github.com/balloob/home-assistant/blob/master/homeassistant/components/api.py#L90) is 50 lines and the [client-side code](https://github.com/balloob/home-assistant-js/blob/master/src/actions/stream.js) is 80 lines of code. Streaming updates has been implemented using the HTML5 `EventSource` tag. Implementation is pretty straight forward as all the reconnection logic will be handled by the event source tag. The [server-side code](https://github.com/balloob/home-assistant/blob/master/homeassistant/components/api.py#L90) is 50 lines and the [client-side code](https://github.com/balloob/home-assistant-js/blob/master/src/actions/stream.js) is 80 lines of code.
All events that happen on the server will now also be sent to the browser. This turns any browser running the UI into a fully functioning [slave instance](https://home-assistant.io/developers/architecture.html#multiple-connected-instances) of Home Assistant. This opens up new possibilities for Home Assistant components that live completely client-side. All events that happen on the server will now also be sent to the browser. This turns any browser running the UI into a fully functioning [slave instance](https://home-assistant.io/developers/architecture/#multiple-connected-instances) of Home Assistant. This opens up new possibilities for Home Assistant components that live completely client-side.
Implementing EventSource was not without challenges. Here are some of the issues that had to be solved: Implementing EventSource was not without challenges. Here are some of the issues that had to be solved:

2
source/_posts/2015-04-25-release-notes.markdown
View File

@ -21,7 +21,7 @@ __ISY994 hub support__<br>
<img src='/images/supported_brands/universal_devices.png' style='border:none; box-shadow: none; float: right;' height='50' /> <img src='/images/supported_brands/universal_devices.png' style='border:none; box-shadow: none; float: right;' height='50' />
[Ryan](https://github.com/rmkraus) has contributed support to integrate the ISY994 hub by Universal Devices. This allows you to integrate your X10/Insteon sensors, switches and lights. [Ryan](https://github.com/rmkraus) has contributed support to integrate the ISY994 hub by Universal Devices. This allows you to integrate your X10/Insteon sensors, switches and lights.
He has created an extensive getting started guide which can be found on [the ISY994 component page](/components/isy994.html). He has created an extensive getting started guide which can be found on [the ISY994 component page](/components/isy994/).
```yaml ```yaml
# Example configuration.yaml entry # Example configuration.yaml entry

2
source/_posts/2015-06-10-release-notes.markdown
View File

@ -145,7 +145,7 @@ notify:
__Swiss Public transport sensor__<br> __Swiss Public transport sensor__<br>
The swiss public transport sensor will give you the next two departure times from a given location to another one in Switzerland. See the [component page](/components/sensor.swiss_public_transport.html) for more information how to set it up. The swiss public transport sensor will give you the next two departure times from a given location to another one in Switzerland. See the [component page](/components/sensor.swiss_public_transport/) for more information how to set it up.
__Transmission turtle mode switch__<br> __Transmission turtle mode switch__<br>

2
source/_posts/2015-07-11-ip-cameras-arduino-kodi-efergy-support.markdown
View File

@ -35,7 +35,7 @@ To update to the latest version, run <code>scripts/update</code>. Please report
__Arduino__<br> __Arduino__<br>
<img src='/images/supported_brands/arduino.png' style='border:none; box-shadow: none; float: right;' height='50' /> <img src='/images/supported_brands/arduino.png' style='border:none; box-shadow: none; float: right;' height='50' />
Fabian has contributed support for interfacing with Arduinos. This makes it possible to connect your Arduino via USB and expose pins as sensor data and write to pins via switches. Have a look at [the docs](/components/arduino.html) for an extensive guide to get started. Fabian has contributed support for interfacing with Arduinos. This makes it possible to connect your Arduino via USB and expose pins as sensor data and write to pins via switches. Have a look at [the docs](/components/arduino/) for an extensive guide to get started.
```yaml ```yaml
# Example configuration.yaml entry # Example configuration.yaml entry

4
source/_posts/2015-08-09-mqtt-raspberry-pi-squeezebox-asuswrt-support.markdown
View File

@ -15,8 +15,8 @@ __MQTT Support__<br>
The big new addition in this release is the support for the MQTT protocol by [@fabaff](https://github.com/fabaff) with some help from [@balloob](https://github.com/balloob). It will now be possible to integrate any IoT device that talks via MQTT. For the initial release we support connecting Home Assistant to a broker (no TLS yet). Components can now subscribe and publish to MQTT topics ([see the example][mqtt-example]) and also support for the automation component [has been added][mqtt-automation]. For more information, see [the MQTT component page][mqtt-component]. The big new addition in this release is the support for the MQTT protocol by [@fabaff](https://github.com/fabaff) with some help from [@balloob](https://github.com/balloob). It will now be possible to integrate any IoT device that talks via MQTT. For the initial release we support connecting Home Assistant to a broker (no TLS yet). Components can now subscribe and publish to MQTT topics ([see the example][mqtt-example]) and also support for the automation component [has been added][mqtt-automation]. For more information, see [the MQTT component page][mqtt-component].
[mqtt-example]: https://github.com/balloob/home-assistant/blob/dev/config/custom_components/mqtt_example.py [mqtt-example]: https://github.com/balloob/home-assistant/blob/dev/config/custom_components/mqtt_example.py
[mqtt-automation]: /components/automation.html#mqtt-based-automation [mqtt-automation]: /components/automation/#mqtt-based-automation
[mqtt-component]: /components/mqtt.html [mqtt-component]: /components/mqtt/
```yaml ```yaml
# Example configuration.yaml entry # Example configuration.yaml entry

6
source/_posts/2015-08-26-laundry-automation-with-moteino-mqtt-and-home-assistant.markdown
View File

@ -14,7 +14,7 @@ _This is a guest post by Home Assistant user and contributor [Nolan Gilley](http
In our house, laundry has been a struggle for quite some time. Our washer and dryer both lack a buzzer which leads to forgotten laundry, and stinky mess that needs to be rewashed. I decided to create a solution by monitoring the washer and dryer myself with some cheap electronics. In our house, laundry has been a struggle for quite some time. Our washer and dryer both lack a buzzer which leads to forgotten laundry, and stinky mess that needs to be rewashed. I decided to create a solution by monitoring the washer and dryer myself with some cheap electronics.
As an avid user of Home Assistant, I decided it would be the perfect application to manage the UI and notification system. Now all I needed was a way to monitor the washer and dryer. I tried using sound sensors but found them unreliable. I ended up opting for an accelerometer attached to the back of each appliance. I also added magnetic reed switches on the doors of the washer and dryer to detect if the doors are open or closed. I connected the accelerometers and reed switches to a [Moteino](https://lowpowerlab.com/moteino/), an arduino clone with an RF transceiver. The Moteino can perform the logic to figure out which state the appliances are in and wirelessly communicate that data with another Moteino that is connected via serial to my Raspberry Pi. The Raspberry Pi reads the serial data and repeats it over MQTT for Home Assistant to use. This is great because I don't have to run Home Assistant on the Raspberry Pi. I can run it on a faster machine and point the [MQTT component](/components/mqtt.html) to my Raspberry Pi. As an avid user of Home Assistant, I decided it would be the perfect application to manage the UI and notification system. Now all I needed was a way to monitor the washer and dryer. I tried using sound sensors but found them unreliable. I ended up opting for an accelerometer attached to the back of each appliance. I also added magnetic reed switches on the doors of the washer and dryer to detect if the doors are open or closed. I connected the accelerometers and reed switches to a [Moteino](https://lowpowerlab.com/moteino/), an arduino clone with an RF transceiver. The Moteino can perform the logic to figure out which state the appliances are in and wirelessly communicate that data with another Moteino that is connected via serial to my Raspberry Pi. The Raspberry Pi reads the serial data and repeats it over MQTT for Home Assistant to use. This is great because I don't have to run Home Assistant on the Raspberry Pi. I can run it on a faster machine and point the [MQTT component](/components/mqtt/) to my Raspberry Pi.
After taking some sample data from the accelerometers while each appliance was in operation, I decided to plot the data to help determine the proper thresholds of when the devices were running or off. I had to do this in order to get precise ranges so the dryer sensor wouldn't get tripped by the washer or vice versa. In the plot below you can see the acceleration in the x direction for the accelerometer connected to the washing machine. It's easy to see when the washing machine is in operation here. I used the same technique for the dryer's accelerometer. After taking some sample data from the accelerometers while each appliance was in operation, I decided to plot the data to help determine the proper thresholds of when the devices were running or off. I had to do this in order to get precise ranges so the dryer sensor wouldn't get tripped by the washer or vice versa. In the plot below you can see the acceleration in the x direction for the accelerometer connected to the washing machine. It's easy to see when the washing machine is in operation here. I used the same technique for the dryer's accelerometer.
@ -27,14 +27,14 @@ After taking some sample data from the accelerometers while each appliance was i
<!--more--> <!--more-->
Next it was just a matter of integrating everything with Home Assistant. I was able to use the [MQTT component](/components/mqtt.html) to read the washer and dryer states from the Moteino and display it in Home Assistant. Next it was just a matter of integrating everything with Home Assistant. I was able to use the [MQTT component](/components/mqtt/) to read the washer and dryer states from the Moteino and display it in Home Assistant.
<p class='img'> <p class='img'>
<img src='/images/blog/2015-08-laundry-automation/screenshot-ha.png' /> <img src='/images/blog/2015-08-laundry-automation/screenshot-ha.png' />
Status of the dryer and washer in Home Assistant Status of the dryer and washer in Home Assistant
</p> </p>
Next I wrote [scripts](/components/script.html) that are run whenever the washer or dryer completes a load. This is triggered by the [automation component](/components/automation.html). When the laundry is complete I have the lights in the house turn red and [notify me via PushBullet](/components/notify.pushbullet.html). Once the laundry is taken care of another script runs that sets the lights back to normal. So far it has been very helpful and very reliable. Next I wrote [scripts](/components/script/) that are run whenever the washer or dryer completes a load. This is triggered by the [automation component](/components/automation/). When the laundry is complete I have the lights in the house turn red and [notify me via PushBullet](/components/notify.pushbullet/). Once the laundry is taken care of another script runs that sets the lights back to normal. So far it has been very helpful and very reliable.
<p class='img'> <p class='img'>
<a href='/images/blog/2015-08-laundry-automation/moteino-and-sensors.jpg'> <a href='/images/blog/2015-08-laundry-automation/moteino-and-sensors.jpg'>

4
source/_posts/2015-08-31-version-7-revamped-ui-and-improved-distribution.markdown
View File

@ -73,8 +73,8 @@ __MQTT Sensors and Switches__<br>
integration with MQTTT: [sensor][mqtt-sensor] and [switch][mqtt-switch]. Both platforms require the integration with MQTTT: [sensor][mqtt-sensor] and [switch][mqtt-switch]. Both platforms require the
MQTT component to be connected to a broker. MQTT component to be connected to a broker.
[mqtt-sensor]: /components/sensor.mqtt.html [mqtt-sensor]: /components/sensor.mqtt/
[mqtt-switch]: /components/switch.mqtt.html [mqtt-switch]: /components/switch.mqtt/
```yaml ```yaml
# Example configuration.yml entr # Example configuration.yml entr

4
source/_posts/2015-09-11-different-ways-to-use-mqtt-with-home-assistant.markdown
View File

@ -11,7 +11,7 @@ og_image: /images/blog/2015-09-mqtt/arduino.png
--- ---
<img src='/images/supported_brands/mqtt.png' style='border:none; box-shadow: none; float: right;' height='80' /> <img src='/images/supported_brands/mqtt.png' style='border:none; box-shadow: none; float: right;' height='80' />
The [MQTT](https://en.wikipedia.org/wiki/MQTT) support was added to Home Assistant recently. The [MQTT component](https://home-assistant.io/components/mqtt.html) will enable you to do all sort of things. Most likely you will use it to communicate with your devices. But Home Assistant doesn't care where the data is coming from or is limited to real hardware as long as there is MQTT support. This means that it doesn't matter if the data is coming from a human, a web service, or a device. The [MQTT](https://en.wikipedia.org/wiki/MQTT) support was added to Home Assistant recently. The [MQTT component](https://home-assistant.io/components/mqtt/) will enable you to do all sort of things. Most likely you will use it to communicate with your devices. But Home Assistant doesn't care where the data is coming from or is limited to real hardware as long as there is MQTT support. This means that it doesn't matter if the data is coming from a human, a web service, or a device.
A great example is shown in a [Laundry Automation](https://home-assistant.io/blog/2015/08/26/laundry-automation-with-moteino-mqtt-and-home-assistant/) post in this blog. A great example is shown in a [Laundry Automation](https://home-assistant.io/blog/2015/08/26/laundry-automation-with-moteino-mqtt-and-home-assistant/) post in this blog.
@ -32,7 +32,7 @@ sensor:
state_topic: "home-assistant/fabian/mood" state_topic: "home-assistant/fabian/mood"
``` ```
After a restart of Home Assistant the "Mood" sensor will show up in the frontend. For more details about the configuration of MQTT itself and the sensor, please refer to the [MQTT component](https://home-assistant.io/components/mqtt.html) or the [MQTT sensor](https://home-assistant.io/components/sensor.mqtt.html) documentation. After a restart of Home Assistant the "Mood" sensor will show up in the frontend. For more details about the configuration of MQTT itself and the sensor, please refer to the [MQTT component](https://home-assistant.io/components/mqtt/) or the [MQTT sensor](https://home-assistant.io/components/sensor.mqtt/) documentation.
Now we can set the mood. The commandline tool (`mosquitto_pub`) which is shipped with `mosquitto` is used to send an MQTT message. Now we can set the mood. The commandline tool (`mosquitto_pub`) which is shipped with `mosquitto` is used to send an MQTT message.

2
source/_posts/2015-09-13-home-assistant-meets-ifttt.markdown
View File

@ -25,7 +25,7 @@ if your smoke alarm goes off.
<img src='/images/blog/2015-09-ifttt/splash.png'> <img src='/images/blog/2015-09-ifttt/splash.png'>
</p> </p>
Head over to the [setup instructions](/components/ifttt.html) to get started with IFTTT. Click the Head over to the [setup instructions](/components/ifttt/) to get started with IFTTT. Click the
read more button for some example recipes. read more button for some example recipes.
<!--more--> <!--more-->

6
source/_posts/2015-09-18-monitoring-with-glances-and-home-assistant.markdown
View File

@ -11,13 +11,13 @@ og_image: /images/supported_brands/glances.png
--- ---
<img src='/images/supported_brands/glances.png' style='border:none; box-shadow: none; float: right;' height='80' /> <img src='/images/supported_brands/glances.png' style='border:none; box-shadow: none; float: right;' height='80' />
Inspried by a [feature requests](https://github.com/balloob/home-assistant/issues/310) I started looking into the available options to do monitoring of remote hosts. The feature request is about displaying system information in a similar way than the [systemmonitor](/components/sensor.systemmonitor.html) sensor does it for the local system. After a while I started to think that it would be a nice addition for a small home network where no full-blown system monitoring setup is present. Inspried by a [feature requests](https://github.com/balloob/home-assistant/issues/310) I started looking into the available options to do monitoring of remote hosts. The feature request is about displaying system information in a similar way than the [systemmonitor](/components/sensor.systemmonitor/) sensor does it for the local system. After a while I started to think that it would be a nice addition for a small home network where no full-blown system monitoring setup is present.
<!--more--> <!--more-->
The basic problem is to get the data from the remote host. Starting with [psutil](https://pypi.python.org/pypi/psutil) that is used by the systemmonitor sensor, a possible solution is only a click away and named [Glances](https://github.com/nicolargo/glances). Glances has a nice curses-based interface and a [RESTful API](https://github.com/nicolargo/glances/wiki/The-Glances-RESTFULL-JSON-API). The basic problem is to get the data from the remote host. Starting with [psutil](https://pypi.python.org/pypi/psutil) that is used by the systemmonitor sensor, a possible solution is only a click away and named [Glances](https://github.com/nicolargo/glances). Glances has a nice curses-based interface and a [RESTful API](https://github.com/nicolargo/glances/wiki/The-Glances-RESTFULL-JSON-API).
The [Glances sensor](/components/sensor.glances.html) sensor uses that API to get all needed data. The [Glances sensor](/components/sensor.glances/) sensor uses that API to get all needed data.
In this post a default Fedora 22 Workstation installation is used on the host that should be monitored. In fact, it doesn't matter if the system is the local one or a remote one as long as Glances is available. With some adjustments it should work on your own systems too. The difference will be the package and the firewall management tools. In this post a default Fedora 22 Workstation installation is used on the host that should be monitored. In fact, it doesn't matter if the system is the local one or a remote one as long as Glances is available. With some adjustments it should work on your own systems too. The difference will be the package and the firewall management tools.
@ -55,7 +55,7 @@ curl -X GET http://IP_ADDRESS:61208/api/2/mem/used
{"used": 203943936} {"used": 203943936}
``` ```
Add the [glances sensor](/components/sensor.glances.html) entry to your `configuration.yaml` file and restart Home Assistant then. Add the [glances sensor](/components/sensor.glances/) entry to your `configuration.yaml` file and restart Home Assistant then.
```yaml ```yaml
# Example configuration.yaml entry # Example configuration.yaml entry

2
source/_posts/2015-09-19-alarm-sonos-and-itunes-support.markdown
View File

@ -42,7 +42,7 @@ media_player:
__Automation__<br> __Automation__<br>
Automation has gotten a lot of love. It now supports conditions, multiple triggers and new types of Automation has gotten a lot of love. It now supports conditions, multiple triggers and new types of
triggers. The best to get started with it is to head over to the new triggers. The best to get started with it is to head over to the new
[getting started with automation](/getting-started/automation.html) page. [getting started with automation](/getting-started/automation/) page.
```yaml ```yaml
# Example of entry in configuration.yaml # Example of entry in configuration.yaml

18
source/_posts/2015-10-05-home-assistant-goes-geo-with-owntracks.markdown
View File

@ -20,10 +20,10 @@ The geo support consists of three different parts:
We have added a new [getting started section][start-presence] to get up and running. We have added a new [getting started section][start-presence] to get up and running.
[platform-owntracks]: /components/device_tracker.owntracks.html [platform-owntracks]: /components/device_tracker.owntracks/
[component-zone]: /components/zone.html [component-zone]: /components/zone/
[zone-automation]: /components/automation.html#zone-trigger [zone-automation]: /components/automation/#zone-trigger
[start-presence]: /getting-started/presence-detection.html [start-presence]: /getting-started/presence-detection/
<p class='img'> <p class='img'>
<img src='/images/screenshots/map.png' /> <img src='/images/screenshots/map.png' />
@ -33,15 +33,15 @@ Map in Home Assistant showing two people and three zones (home, school, work)
Ofcourse more things happened in the last three weeks. I'm moving away from my usual long post to a Ofcourse more things happened in the last three weeks. I'm moving away from my usual long post to a
short summary of highlights: short summary of highlights:
<a href='/components/media_player.plex.html'> <a href='/components/media_player.plex/'>
<img src='/images/supported_brands/plex.png' style='border:none; box-shadow: none; float: right;' height='50' /> <img src='/images/supported_brands/plex.png' style='border:none; box-shadow: none; float: right;' height='50' />
</a> </a>
- Sensor: [rest platform](/components/sensor.rest.html) added ([@fabaff](https://github.com/fabaff)) - Sensor: [rest platform](/components/sensor.rest/) added ([@fabaff](https://github.com/fabaff))
- Alarm Control Panel: [MQTT platform](/components/alarm_control_panel.mqtt.html) added ([@sfam](https://github.com/sfam)) - Alarm Control Panel: [MQTT platform](/components/alarm_control_panel.mqtt/) added ([@sfam](https://github.com/sfam))
- Media Player: [Plex platform](/components/media_player.plex.html) added ([@miniconfig](https://github.com/miniconfig, [@adrienbrault](https://github.com/adrienbrault)) - Media Player: [Plex platform](/components/media_player.plex/) added ([@miniconfig](https://github.com/miniconfig, [@adrienbrault](https://github.com/adrienbrault))
- Dev Tools: services can now show description of fields ([@balloob](https://github.com/balloob)) - Dev Tools: services can now show description of fields ([@balloob](https://github.com/balloob))
- MQTT: Support for certificates and improved error reporting ([@balloob](https://github.com/balloob)) - MQTT: Support for certificates and improved error reporting ([@balloob](https://github.com/balloob))
- Light: [limitlessled platform](/components/light.limitlessled.html) extended with white light support ([@auchter](https://github.com/auchter)) - Light: [limitlessled platform](/components/light.limitlessled/) extended with white light support ([@auchter](https://github.com/auchter))
- Fuzzy matching for scenes ([@pavoni](https://github.com/pavoni)) - Fuzzy matching for scenes ([@pavoni](https://github.com/pavoni))
- Scene support for media player ([@maddox](https://github.com/maddox)) - Scene support for media player ([@maddox](https://github.com/maddox))

2
source/_posts/2015-10-11-measure-temperature-with-esp8266-and-report-to-mqtt.markdown
View File

@ -34,7 +34,7 @@ I've been using Adafruit for my shopping:
- [Adafruit HUZZAH ESP8266 Breakout](http://www.adafruit.com/product/2471) ([assembly instructions](https://learn.adafruit.com/adafruit-huzzah-esp8266-breakout/assembly)) - [Adafruit HUZZAH ESP8266 Breakout](http://www.adafruit.com/product/2471) ([assembly instructions](https://learn.adafruit.com/adafruit-huzzah-esp8266-breakout/assembly))
- [Adafruit HDC1008 Temperature & Humidity Sensor Breakout Board](http://www.adafruit.com/product/2635) ([assembly instructions](https://learn.adafruit.com/adafruit-hdc1008-temperature-and-humidity-sensor-breakout/assembly)) - [Adafruit HDC1008 Temperature & Humidity Sensor Breakout Board](http://www.adafruit.com/product/2635) ([assembly instructions](https://learn.adafruit.com/adafruit-hdc1008-temperature-and-humidity-sensor-breakout/assembly))
- [MQTT server](/components/mqtt.html#picking-a-broker) - [MQTT server](/components/mqtt/#picking-a-broker)
_Besides this, you will need the usual hardware prototype equipment: a breadboard, some wires, _Besides this, you will need the usual hardware prototype equipment: a breadboard, some wires,
soldering iron + wire, Serial USB cable._ soldering iron + wire, Serial USB cable._

12
source/_posts/2015-10-11-rfxtrx-blinkstick-and-snmp-support.markdown
View File

@ -20,11 +20,11 @@ This release also includes some new platforms (because they keep coming!):
<img src='/images/supported_brands/rfxtrx.png' style='border:none; box-shadow: none; float: right; clear: right;' height='50' /> <img src='/images/supported_brands/rfxtrx.png' style='border:none; box-shadow: none; float: right; clear: right;' height='50' />
<img src='/images/supported_brands/telegram.png' style='border:none; box-shadow: none; float: right; clear: right;' height='50' /> <img src='/images/supported_brands/telegram.png' style='border:none; box-shadow: none; float: right; clear: right;' height='50' />
- Light: [blinkstick platform](/components/light.blinksticklight.html) added ([@alanbowman](https://github.com/alanbowman)) - Light: [blinkstick platform](/components/light.blinksticklight/) added ([@alanbowman](https://github.com/alanbowman))
- Device Tracker: [SNMP platform](/components/device_tracker.snmp.html) added ([@tomduijf](https://github.com/tomduijf)) - Device Tracker: [SNMP platform](/components/device_tracker.snmp/) added ([@tomduijf](https://github.com/tomduijf))
- Light: [rfxtrx platform](/components/light.rfxtrx.html) added ([@badele](https://github.com/badele)) - Light: [rfxtrx platform](/components/light.rfxtrx/) added ([@badele](https://github.com/badele))
- Switch: [rfxtrx platform](/components/switch.rfxtrx.html) added ([@badele](https://github.com/badele)) - Switch: [rfxtrx platform](/components/switch.rfxtrx/) added ([@badele](https://github.com/badele))
- Notify: [telegram platform](/components/notify.telegram.html) added ([@fabaff](https://github.com/fabaff)) - Notify: [telegram platform](/components/notify.telegram/) added ([@fabaff](https://github.com/fabaff))
Also, the media player was extended by [@maddox](https://github.com/maddox) to support the play media command. Also, the media player was extended by [@maddox](https://github.com/maddox) to support the play media command.
This has been implemented for the [iTunes platform](/components/media_player.itunes.html). This has been implemented for the [iTunes platform](/components/media_player.itunes/).

34
source/_posts/2015-10-26-firetv-and-radiotherm-now-supported.markdown
View File

@ -21,22 +21,22 @@ complete revamp.
<img src='/images/supported_brands/firetv.png' style='border:none; box-shadow: none; float: right; margin-bottom: 16px; clear: right;' height='50' /> <img src='/images/supported_brands/firetv.png' style='border:none; box-shadow: none; float: right; margin-bottom: 16px; clear: right;' height='50' />
<img src='/images/supported_brands/geofancy.png' style='border:none; box-shadow: none; float: right; margin-bottom: 16px; clear: right;' height='50' /> <img src='/images/supported_brands/geofancy.png' style='border:none; box-shadow: none; float: right; margin-bottom: 16px; clear: right;' height='50' />
- Device tracker: Newer [TP-Link routers](/components/device_tracker.tplink.html) now supported ([@mKeRix](https://github.com/mKeRix)) - Device tracker: Newer [TP-Link routers](/components/device_tracker.tplink/) now supported ([@mKeRix](https://github.com/mKeRix))
- Alarm Control Panel: [Manual alarm](/components/alarm_control_panel.manual.html) added ([@sfam](https://github.com/sfam)) - Alarm Control Panel: [Manual alarm](/components/alarm_control_panel.manual/) added ([@sfam](https://github.com/sfam))
- Thermostat: [Radiotherm](/components/thermostat.radiotherm.html) now supported ([@toddeye](https://github.com/toddeye)) - Thermostat: [Radiotherm](/components/thermostat.radiotherm/) now supported ([@toddeye](https://github.com/toddeye))
- Media Player: [Amazon FireTV](/components/media_player.firetv.html) now supported ([@happyleavesaoc](https://github.com/happyleavesaoc)) - Media Player: [Amazon FireTV](/components/media_player.firetv/) now supported ([@happyleavesaoc](https://github.com/happyleavesaoc))
- Device Tracker: [Geofancy](/components/device_tracker.geofancy.html) now supported ([@wind-rider](https://github.com/wind-rider)) - Device Tracker: [Geofancy](/components/device_tracker.geofancy/) now supported ([@wind-rider](https://github.com/wind-rider))
- New component [Shell Command](/components/shell_command.html) can expose shell commands as services ([@balloob](https://github.com/balloob)) - New component [Shell Command](/components/shell_command/) can expose shell commands as services ([@balloob](https://github.com/balloob))
- [Scripts](/components/script.html) can now be customized using `customize` key in `configuration.yaml` ([@balloob](https://github.com/balloob)) - [Scripts](/components/script/) can now be customized using `customize` key in `configuration.yaml` ([@balloob](https://github.com/balloob))
- Light: [Hyperion](/components/light.hyperion.html) now supported ([@MakeMeASandwich](https://github.com/MakeMeASandwich)) - Light: [Hyperion](/components/light.hyperion/) now supported ([@MakeMeASandwich](https://github.com/MakeMeASandwich))
- Sensor: [aRest](/components/sensor.arest.html) can now also read out pins ([@balloob](https://github.com/balloob)) - Sensor: [aRest](/components/sensor.arest/) can now also read out pins ([@balloob](https://github.com/balloob))
- Sensor: [Forecast.io](/components/sensor.forecast.html) now supports specifying units in `configuration.yaml` ([@balloob](https://github.com/balloob)) - Sensor: [Forecast.io](/components/sensor.forecast/) now supports specifying units in `configuration.yaml` ([@balloob](https://github.com/balloob))
- Thermostat: [Heat Control](/components/thermostat.heat_control.html) has been completely rewritten ([@balloob](https://github.com/balloob)) - Thermostat: [Heat Control](/components/thermostat.heat_control/) has been completely rewritten ([@balloob](https://github.com/balloob))
- Switch: [Rest](/components/switch.rest.html) now supported ([@bachp](https://github.com/bachp)) - Switch: [Rest](/components/switch.rest/) now supported ([@bachp](https://github.com/bachp))
- Media Player: [Plex](/components/media_player.plex.html) can now be auto discovered and configure itself ([@tomduijf](https://github.com/tomduijf)) - Media Player: [Plex](/components/media_player.plex/) can now be auto discovered and configure itself ([@tomduijf](https://github.com/tomduijf))
- [Downloader](/components/downloader.html) will now treat relative paths based on config dir ([@tomduijf](https://github.com/tomduijf)) - [Downloader](/components/downloader/) will now treat relative paths based on config dir ([@tomduijf](https://github.com/tomduijf))
- Line Charts will use interpolation for sensor data and show current and target temperature for thermostats ([@balloob](https://github.com/balloob)) - Line Charts will use interpolation for sensor data and show current and target temperature for thermostats ([@balloob](https://github.com/balloob))
- Device Tracker: [OpenWRT via ubus](/components/device_tracker.ubus.html) now supported ([@krzynio](https://github.com/krzynio)) - Device Tracker: [OpenWRT via ubus](/components/device_tracker.ubus/) now supported ([@krzynio](https://github.com/krzynio))
<!--more--> <!--more-->
@ -45,11 +45,11 @@ complete revamp.
As part of this release we did some cleanup which introduced backwards incompatible changes: As part of this release we did some cleanup which introduced backwards incompatible changes:
**Heat Control thermostat no longer includes scheduling features.**<br> **Heat Control thermostat no longer includes scheduling features.**<br>
This feature has been removed completely. Use the [automation component](/components/automation.html) This feature has been removed completely. Use the [automation component](/components/automation/)
instead to control target temperature. instead to control target temperature.
**Config changed for calling a service from a script.**<br> **Config changed for calling a service from a script.**<br>
`execute_service:` has been replaced with `service:`. See [component page](/components/script.html) `execute_service:` has been replaced with `service:`. See [component page](/components/script/)
for example. The old method will continue working for some time. for example. The old method will continue working for some time.
**Scenes can no longer be turned off.**<br> **Scenes can no longer be turned off.**<br>

2
source/developers/add_new_platform.markdown
View File

@ -28,7 +28,7 @@ devices but use a third-party Python 3 library to do so. This way Home Assistant
code with the Python community and we can keep the project maintainable. code with the Python community and we can keep the project maintainable.
Platforms can specify dependencies and requirements the same way as a component does. Please see Platforms can specify dependencies and requirements the same way as a component does. Please see
[the component page](/developers/creating_components.html#dependencies) for more information. [the component page](/developers/creating_components/#dependencies) for more information.
### {% linkable_title Creating Entities %} ### {% linkable_title Creating Entities %}

4
source/developers/api.markdown
View File

@ -12,5 +12,5 @@ footer: true
Home Assistant is offering a RESTful API and a Python API for convenient access to Home Assistant is offering a RESTful API and a Python API for convenient access to
a Home Assistant instance over HTTP. a Home Assistant instance over HTTP.
- [Rest API](/developers/rest_api.html) - [Rest API](/developers/rest_api/)
- [Python API](/developers/python_api.html) - [Python API](/developers/python_api/)

2
source/developers/architecture.markdown
View File

@ -47,7 +47,7 @@ These components will track devices within a specific domain and exist of a core
For example, one of the built-in components is the `switch` component. This component is responsible for interaction with different types of switches. For example, one of the built-in components is the `switch` component. This component is responsible for interaction with different types of switches.
If you are planning to add support for a new platform, please check out the [add new platform section]({{root_url}}/developers/add_new_platform.html). If you are planning to add support for a new platform, please check out the [add new platform section]({{root_url}}/developers/add_new_platform/).
#### {% linkable_title Components that respond to events that happen within Home Assistant %} #### {% linkable_title Components that respond to events that happen within Home Assistant %}
These components provide small pieces of home automation logic or services that do common tasks within your house. These components provide small pieces of home automation logic or services that do common tasks within your house.

2
source/developers/frontend.markdown
View File

@ -73,7 +73,7 @@ Building a new version of the frontend is as simple as running `script/build_fro
* Vulcanize all Webcomponents to `frontend.vulcan.html`. * Vulcanize all Webcomponents to `frontend.vulcan.html`.
* Minify `frontend.vulcan.html` and save it as `frontend.html`. * Minify `frontend.vulcan.html` and save it as `frontend.html`.
* Copy the webcomponents polyfill `webcomponents-lite.min.js` from **home-assistant-polymer** to `components/frontend/www_static/webcomponents-lite.min.js`. * Copy the webcomponents polyfill `webcomponents-lite.min.js` from **home-assistant-polymer** to `components/frontend/www_static/webcomponents-lite.min.js`.
* Copy the final frontend build `frontend.html` from **home-assistant-polymer** to `components/frontend/www_static/frontend.html`. * Copy the final frontend build `frontend.html` from **home-assistant-polymer** to `components/frontend/www_static/frontend/`.
* Generate MD5 hash of `frontend.html` to signal caches to redownload the UI. * Generate MD5 hash of `frontend.html` to signal caches to redownload the UI.
<p class='img'> <p class='img'>

12
source/developers/index.markdown
View File

@ -51,10 +51,10 @@ requests.
### {% linkable_title Further reading %} ### {% linkable_title Further reading %}
- [Home Assistant Architecture](/developers/architecture.html) - [Home Assistant Architecture](/developers/architecture/)
- [Frontend development](/developers/frontend.html) - [Frontend development](/developers/frontend/)
- [Creating a custom component](/developers/creating_components.html) - [Creating a custom component](/developers/creating_components/)
- [Adding support for a new platform](/developers/add_new_platform.html) - [Adding support for a new platform](/developers/add_new_platform/)
- [Rest API](/developers/api.html) - [Rest API](/developers/api/)
- [Website](/developers/website.html) - [Website](/developers/website/)

2
source/developers/python_api.markdown
View File

@ -9,7 +9,7 @@ sharing: true
footer: true footer: true
--- ---
In the package [`homeassistant.remote`](https://github.com/balloob/home-assistant/blob/master/homeassistant/remote.py) a Python API on top of the [HTTP API](/developers/api.html) can be found. In the package [`homeassistant.remote`](https://github.com/balloob/home-assistant/blob/master/homeassistant/remote.py) a Python API on top of the [HTTP API](/developers/api/) can be found.
This page is not a full documentation it's more a collection of some example. A simple way to get all current entities is to visit the "Set State" page in the "Developer Tools". For the examples below just choose one from the available entries. Here the sensor `sensor.office_temperature` and the switch `switch.livingroom_pin_2` are used. This page is not a full documentation it's more a collection of some example. A simple way to get all current entities is to visit the "Set State" page in the "Developer Tools". For the examples below just choose one from the available entries. Here the sensor `sensor.office_temperature` and the switch `switch.livingroom_pin_2` are used.

10
source/getting-started/automation.markdown
View File

@ -11,7 +11,7 @@ footer: true
When all your devices are set up it's time to put the cherry on the pie: automation. Home Assistant When all your devices are set up it's time to put the cherry on the pie: automation. Home Assistant
offers [a few built-in automations](/components/#automation) but mainly you'll be using offers [a few built-in automations](/components/#automation) but mainly you'll be using
[the automation component](/components/automation.html) to set up your own rules. [the automation component](/components/automation/) to set up your own rules.
### {% linkable_title The basics of automation %} ### {% linkable_title The basics of automation %}
@ -165,10 +165,10 @@ automation:
We went over the basics of creating a home automation rule. From here no longer any hand holding, We went over the basics of creating a home automation rule. From here no longer any hand holding,
go automate! go automate!
- Learn about the available [automation triggers](/components/automation.html#triggers) - Learn about the available [automation triggers](/components/automation/#triggers)
- Learn about the available [automation conditions](/components/automation.html#conditions) - Learn about the available [automation conditions](/components/automation/#conditions)
- Learn about [scripts](/components/script.html) to help you trigger multiple actions and delays - Learn about [scripts](/components/script/) to help you trigger multiple actions and delays
- Learn about [scenes](/components/scene.html) to help you set many entities at once to your liking - Learn about [scenes](/components/scene/) to help you set many entities at once to your liking
- Setup the [notification component](/components/#notify-service) to sent yourself messages - Setup the [notification component](/components/#notify-service) to sent yourself messages
<p class='note warning'> <p class='note warning'>

2
source/getting-started/autostart.markdown
View File

@ -125,4 +125,4 @@ Home Assistant has been uninstalled.
</div> <!-- OSX --> </div> <!-- OSX -->
###[&laquo; Back to Getting Started](/getting-started/index.html) ###[&laquo; Back to Getting Started](/getting-started/index/)

6
source/getting-started/configuration.markdown
View File

@ -22,7 +22,7 @@ interface and device discovery. It can take up to a minute for your devices to b
show up in the interface. show up in the interface.
If you are running into troubles while configuring Home Assistant, have a look at If you are running into troubles while configuring Home Assistant, have a look at
[the configuration troubleshoot page](/getting-started/troubleshooting-configuration.html). [the configuration troubleshoot page](/getting-started/troubleshooting-configuration/).
<p class='note'> <p class='note'>
You will have to restart Home Assistant for changes in <code>configuration.yaml</code> to take effect. You will have to restart Home Assistant for changes in <code>configuration.yaml</code> to take effect.
@ -64,7 +64,7 @@ http:
### {% linkable_title Setting up your phone or tablet %} ### {% linkable_title Setting up your phone or tablet %}
Home Assistant runs as a self hosted web application. Home Assistant contains support to be added to your homescreen. If you're on Android you can follow [the visual guide]({{site_root}}/getting-started/android.html). For other devices, open Home Assistant on your mobile browser and click on the add to homescreen option. Home Assistant runs as a self hosted web application. Home Assistant contains support to be added to your homescreen. If you're on Android you can follow [the visual guide]({{site_root}}/getting-started/android/). For other devices, open Home Assistant on your mobile browser and click on the add to homescreen option.
### {% linkable_title Remote access %} ### {% linkable_title Remote access %}
@ -76,4 +76,4 @@ Some internet service providers will only offer dynamic IPs. This can cause you
access Home Assistant while being remote. You can solve this by using a free Dynamic DNS service access Home Assistant while being remote. You can solve this by using a free Dynamic DNS service
like [DuckDNS](https://www.duckdns.org/). like [DuckDNS](https://www.duckdns.org/).
###[Next step: Setting up devices &raquo;](/getting-started/devices.html) ###[Next step: Setting up devices &raquo;](/getting-started/devices/)

6
source/getting-started/devices.markdown
View File

@ -11,7 +11,7 @@ footer: true
Home Assistant will be able to automatically discover and configure any Google Chromecasts, Netgear Home Assistant will be able to automatically discover and configure any Google Chromecasts, Netgear
routers, Belkin WeMo switches, Philips Hue bridges and Sonos speakers in your network if you have routers, Belkin WeMo switches, Philips Hue bridges and Sonos speakers in your network if you have
[the discovery component]({{site_root}}/components/discovery.html) enabled (which is by default). [the discovery component]({{site_root}}/components/discovery/) enabled (which is by default).
See the [components overview page](/components/) to find installation instructions for your devices See the [components overview page](/components/) to find installation instructions for your devices
and services. Many components use the `sensor` platform. Sensors need to be added into the `configuration.yaml` as `sensor:`, `sensor 2:`, `sensor 3:`, etc. There should not be gaps in the sequence or your sensors might not load correctly. and services. Many components use the `sensor` platform. Sensors need to be added into the `configuration.yaml` as `sensor:`, `sensor 2:`, `sensor 3:`, etc. There should not be gaps in the sequence or your sensors might not load correctly.
@ -20,7 +20,7 @@ Most components that support multiple entries within the <code>configuration.yam
</p> </p>
If you can't find support for your favorite device or service, If you can't find support for your favorite device or service,
[consider adding support](/developers/add_new_platform.html) [consider adding support](/developers/add_new_platform/)
### {% linkable_title Grouping devices %} ### {% linkable_title Grouping devices %}
@ -60,4 +60,4 @@ homeassistant:
``` ```
###[Next step: Setting up presence detection &raquo;](/getting-started/presence-detection.html) ###[Next step: Setting up presence detection &raquo;](/getting-started/presence-detection/)

6
source/getting-started/index.markdown
View File

@ -77,7 +77,7 @@ Running these commands will:
### {% linkable_title Troubleshooting %} ### {% linkable_title Troubleshooting %}
If you run into any issues, please see [the troubleshooting page](/getting-started/troubleshooting.html). It contains solutions to many of the more commonly encountered issues. If you run into any issues, please see [the troubleshooting page](/getting-started/troubleshooting/). It contains solutions to many of the more commonly encountered issues.
For additional help, in addition to this site, there are three sources: For additional help, in addition to this site, there are three sources:
@ -86,7 +86,7 @@ For additional help, in addition to this site, there are three sources:
- [GitHub Page](https://github.com/balloob/home-assistant) for issue reporting. - [GitHub Page](https://github.com/balloob/home-assistant) for issue reporting.
### {% linkable_title What's next %} ### {% linkable_title What's next %}
If you want to have Home Assistant start on boot, [autostart instructions](/getting-started/autostart.html) can be found here. If you want to have Home Assistant start on boot, [autostart instructions](/getting-started/autostart/) can be found here.
To see what Home Assistant can do, launch demo mode: To see what Home Assistant can do, launch demo mode:
```bash ```bash
@ -98,4 +98,4 @@ To update Home Assistant to the latest release:
pip3 install \-\-upgrade homeassistant pip3 install \-\-upgrade homeassistant
``` ```
###[Next step: Configuring Home Assistant &raquo;](/getting-started/configuration.html) ###[Next step: Configuring Home Assistant &raquo;](/getting-started/configuration/)

18
source/getting-started/presence-detection.markdown
View File

@ -39,7 +39,7 @@ idle, marking them as not home while they are not.
Home Assistant currently supports one third party service for presence detection: [OwnTracks](http://www.owntracks.org). Home Assistant currently supports one third party service for presence detection: [OwnTracks](http://www.owntracks.org).
OwnTracks is an app that you install on your iPhone or Android phone that allows you to push the location OwnTracks is an app that you install on your iPhone or Android phone that allows you to push the location
of your device to Home Assistant using an MQTT broker. An MQTT broker is an Internet of Things communication of your device to Home Assistant using an MQTT broker. An MQTT broker is an Internet of Things communication
platform that you can [freely host yourself][mqtt-self] or get [a private instance for free in the cloud](/components/mqtt.html#run-your-own). platform that you can [freely host yourself][mqtt-self] or get [a private instance for free in the cloud](/components/mqtt/#run-your-own).
<p class='note'> <p class='note'>
OwnTracks communicates directly with your MQTT broker, no data will pass through their servers. OwnTracks communicates directly with your MQTT broker, no data will pass through their servers.
@ -53,14 +53,14 @@ zones][zone] you will be able to add names to locations of your devices. This wa
spot on the state page where the people in your house are and use it as [triggers][trigger] and spot on the state page where the people in your house are and use it as [triggers][trigger] and
[conditions][condition] for automation. [conditions][condition] for automation.
###[Next step: Setting up automation &raquo;](/getting-started/automation.html) ###[Next step: Setting up automation &raquo;](/getting-started/automation/)
[routers]: /components/#presence [routers]: /components/#presence
[nmap]: /components/device_tracker.nmap_scanner.html [nmap]: /components/device_tracker.nmap_scanner/
[ha-owntracks]: /components/device_tracker.owntracks.html [ha-owntracks]: /components/device_tracker.owntracks/
[mqtt-self]: /components/mqtt.html#run-your-own [mqtt-self]: /components/mqtt/#run-your-own
[mqtt-cloud]: /components/mqtt.html#cloudmqtt [mqtt-cloud]: /components/mqtt/#cloudmqtt
[zone]: /components/zone.html [zone]: /components/zone/
[trigger]: /components/automation.html#zone-trigger [trigger]: /components/automation/#zone-trigger
[condition]: /components/automation.html#zone-condition [condition]: /components/automation/#zone-condition

2
source/getting-started/troubleshooting.markdown
View File

@ -68,4 +68,4 @@ iptables -I INPUT -p tcp --dport 8123 -j ACCEPT
iptables-save > /etc/network/iptables.rules # your rules may be saved elsewhere iptables-save > /etc/network/iptables.rules # your rules may be saved elsewhere
``` ```
###[&laquo; Back to Getting Started](/getting-started/index.html) ###[&laquo; Back to Getting Started](/getting-started/index/)