From e59252a39b95c46a75a9ec507c74fc2f22ec5f2a Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Mon, 26 Oct 2015 23:24:55 -0700 Subject: [PATCH] Convert subpages to folders --- .../_components/alarm_control_panel.markdown | 6 ++-- source/_components/arduino.markdown | 4 +-- source/_components/automation.markdown | 10 +++--- .../device_sun_light_trigger.markdown | 2 +- .../device_tracker.actiontec.markdown | 2 +- .../_components/device_tracker.aruba.markdown | 2 +- .../device_tracker.asuswrt.markdown | 2 +- .../_components/device_tracker.ddwrt.markdown | 2 +- .../_components/device_tracker.luci.markdown | 4 +-- source/_components/device_tracker.markdown | 2 +- .../device_tracker.netgear.markdown | 2 +- .../device_tracker.nmap_scanner.markdown | 2 +- .../device_tracker.owntracks.markdown | 4 +-- .../_components/device_tracker.snmp.markdown | 2 +- .../device_tracker.thomson.markdown | 2 +- .../device_tracker.tomato.markdown | 2 +- .../device_tracker.tplink.markdown | 2 +- .../_components/device_tracker.ubus.markdown | 4 +-- source/_components/discovery.markdown | 2 +- source/_components/ifttt.manything.markdown | 2 +- source/_components/ifttt.markdown | 2 +- source/_components/light.hue.markdown | 2 +- source/_components/light.markdown | 4 +-- source/_components/light.wink.markdown | 2 +- source/_components/media_player.cast.markdown | 2 +- source/_components/media_player.plex.markdown | 2 +- source/_components/modbus.markdown | 4 +-- source/_components/mqtt.markdown | 14 ++++---- source/_components/notify.file.markdown | 2 +- source/_components/notify.instapush.markdown | 2 +- source/_components/notify.markdown | 2 +- source/_components/notify.nma.markdown | 2 +- source/_components/notify.pushbullet.markdown | 2 +- source/_components/notify.pushover.markdown | 2 +- source/_components/notify.slack.markdown | 2 +- source/_components/notify.smtp.markdown | 2 +- source/_components/notify.syslog.markdown | 2 +- source/_components/notify.telegram.markdown | 2 +- source/_components/notify.xmpp.markdown | 2 +- .../sensor.command_sensor.markdown | 2 +- source/_components/sensor.rest.markdown | 2 +- source/_components/sensor.wink.markdown | 2 +- source/_components/simple_alarm.markdown | 4 +-- source/_components/sun.markdown | 2 +- .../switch.command_switch.markdown | 2 +- source/_components/switch.wink.markdown | 2 +- source/_components/vera.markdown | 6 ++-- source/_components/zone.markdown | 2 +- .../automation_for_rainy_days.markdown | 2 +- .../asides/component_navigation.html | 2 +- source/_includes/custom/grid_item_left.html | 28 +++++++-------- source/_includes/custom/navigation.html | 20 +++++------ ...rapping-your-setup-with-discovery.markdown | 2 +- .../2015-02-24-streaming-updates.markdown | 2 +- .../_posts/2015-04-25-release-notes.markdown | 2 +- .../_posts/2015-06-10-release-notes.markdown | 2 +- ...meras-arduino-kodi-efergy-support.markdown | 2 +- ...rry-pi-squeezebox-asuswrt-support.markdown | 4 +-- ...h-moteino-mqtt-and-home-assistant.markdown | 6 ++-- ...mped-ui-and-improved-distribution.markdown | 4 +-- ...s-to-use-mqtt-with-home-assistant.markdown | 4 +-- ...-09-13-home-assistant-meets-ifttt.markdown | 2 +- ...g-with-glances-and-home-assistant.markdown | 6 ++-- ...19-alarm-sonos-and-itunes-support.markdown | 2 +- ...assistant-goes-geo-with-owntracks.markdown | 18 +++++----- ...e-with-esp8266-and-report-to-mqtt.markdown | 2 +- ...fxtrx-blinkstick-and-snmp-support.markdown | 12 +++---- ...retv-and-radiotherm-now-supported.markdown | 34 +++++++++---------- source/developers/add_new_platform.markdown | 2 +- source/developers/api.markdown | 4 +-- source/developers/architecture.markdown | 2 +- source/developers/frontend.markdown | 2 +- source/developers/index.markdown | 12 +++---- source/developers/python_api.markdown | 2 +- source/getting-started/automation.markdown | 10 +++--- source/getting-started/autostart.markdown | 2 +- source/getting-started/configuration.markdown | 6 ++-- source/getting-started/devices.markdown | 6 ++-- source/getting-started/index.markdown | 6 ++-- .../presence-detection.markdown | 18 +++++----- .../getting-started/troubleshooting.markdown | 2 +- 81 files changed, 184 insertions(+), 184 deletions(-) diff --git a/source/_components/alarm_control_panel.markdown b/source/_components/alarm_control_panel.markdown index 07afeef3139..ec617fa3e9a 100644 --- a/source/_components/alarm_control_panel.markdown +++ b/source/_components/alarm_control_panel.markdown @@ -12,7 +12,7 @@ footer: true Home Assistant can give you an interface with is similar to a classic alarm system. There are several panels supported: -- [Manual](/components/alarm_control_panel.manual.html) -- [MQTT](/components/alarm_control_panel.mqtt.html) -- [Verisure](/components/verisure.html) +- [Manual](/components/alarm_control_panel.manual/) +- [MQTT](/components/alarm_control_panel.mqtt/) +- [Verisure](/components/verisure/) diff --git a/source/_components/arduino.markdown b/source/_components/arduino.markdown index ab44fb2745e..fcd64090471 100644 --- a/source/_components/arduino.markdown +++ b/source/_components/arduino.markdown @@ -46,6 +46,6 @@ A word of caution: The Arduino boards are not storing states. This means that wi ## Building on top of the Arduino component - - [Arduino Sensor](/components/sensor.arduino.html) - - [Arduino Switch](/components/switch.arduino.html) + - [Arduino Sensor](/components/sensor.arduino/) + - [Arduino Switch](/components/switch.arduino/) diff --git a/source/_components/automation.markdown b/source/_components/automation.markdown index e51ba2c39a4..aa05fcd47bf 100644 --- a/source/_components/automation.markdown +++ b/source/_components/automation.markdown @@ -11,7 +11,7 @@ ha_category: Automation --- This page will go into more detail about the various options the `automation` component offers. If -you haven't yet, read the [getting started page on automation](/getting-started/automation.html). +you haven't yet, read the [getting started page on automation](/getting-started/automation/). A configuration section of an automation requires a `trigger` and an `action` section. `condition` and `condition_type` are optional. To keep this page compact, all following sections will not show the @@ -185,7 +185,7 @@ The above example will trigger on Saturday and Sunday every hour on the 5 (2:05, #### {% linkable_title Zone trigger %} Zone triggers can trigger when an entity is entering or leaving the zone. For zone automation to work, you need to have setup a device tracker platform that supports reporting GPS coordinates. Currently -this is limited to the [OwnTracks platform](/components/device_tracker.owntracks.html). +this is limited to the [OwnTracks platform](/components/device_tracker.owntracks/). ```yaml automation: @@ -273,7 +273,7 @@ Valid values for `weekday` are (sun, mon, tue, wed, thu, fri & sat) #### {% linkable_title Zone condition %} Zone conditions test if an entity is in a certain zone. For zone automation to work, you need to have setup a device tracker platform that supports reporting GPS coordinates. Currently -this is limited to the [OwnTracks platform](/components/device_tracker.owntracks.html). +this is limited to the [OwnTracks platform](/components/device_tracker.owntracks/). ```yaml automation: @@ -311,8 +311,8 @@ automation: ``` If you want to specify multiple services to be called or include a delay, have a look at the -[script component](/components/script.html). If you want to describe how certain entities should look, -check out the [scene component](/components/scene.html). +[script component](/components/script/). If you want to describe how certain entities should look, +check out the [scene component](/components/scene/). ## {% linkable_title Troubleshooting %} diff --git a/source/_components/device_sun_light_trigger.markdown b/source/_components/device_sun_light_trigger.markdown index e566c7ea3cc..391b475c531 100644 --- a/source/_components/device_sun_light_trigger.markdown +++ b/source/_components/device_sun_light_trigger.markdown @@ -16,7 +16,7 @@ Home Assistant has a built-in component called `device_sun_light_trigger` to hel * Turn on the lights when people get home after the sun has set * Turn off the lights when all people leave the house -This component requires the components [sun](/components/sun.html), [device_tracker](/components/device_tracker.html) and [light](/components/light.html) to be enabled. +This component requires the components [sun](/components/sun/), [device_tracker](/components/device_tracker/) and [light](/components/light/) to be enabled. To enable this component, add the following lines to your `configuration.yaml` file: diff --git a/source/_components/device_tracker.actiontec.markdown b/source/_components/device_tracker.actiontec.markdown index 818c82d9224..6e23ceb6577 100644 --- a/source/_components/device_tracker.actiontec.markdown +++ b/source/_components/device_tracker.actiontec.markdown @@ -39,5 +39,5 @@ Configuration variables: - **password** (*Required*): The password for your given admin account. - **home_interval** (*Optional*): If the home_interval is set then the component will not let a device be AWAY if it has been HOME in the last home_interval minutes. This is in addition to the 3 minute wait built into the device_tracker component. -See the [device tracker component page](/components/device_tracker.html) for instructions how to configure the people to be tracked. +See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked. diff --git a/source/_components/device_tracker.aruba.markdown b/source/_components/device_tracker.aruba.markdown index 56f11c2f43b..463034bb2e6 100644 --- a/source/_components/device_tracker.aruba.markdown +++ b/source/_components/device_tracker.aruba.markdown @@ -37,5 +37,5 @@ Configuration variables: - **username** *Required*: The username of an user with administrative privileges, usually *admin*. - **password** *Required*: The password for your given admin account. -See the [device tracker component page](/components/device_tracker.html) for instructions how to configure the people to be tracked. +See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked. diff --git a/source/_components/device_tracker.asuswrt.markdown b/source/_components/device_tracker.asuswrt.markdown index 21a090edefa..9b518a28719 100644 --- a/source/_components/device_tracker.asuswrt.markdown +++ b/source/_components/device_tracker.asuswrt.markdown @@ -35,4 +35,4 @@ Configuration variables: - **username** (*Required*: The username of an user with administrative privileges, usually *admin*. - **password** (*Required*): The password for your given admin account. -See the [device tracker component page](/components/device_tracker.html) for instructions how to configure the people to be tracked. +See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked. diff --git a/source/_components/device_tracker.ddwrt.markdown b/source/_components/device_tracker.ddwrt.markdown index cd4f644c929..741959d19e1 100644 --- a/source/_components/device_tracker.ddwrt.markdown +++ b/source/_components/device_tracker.ddwrt.markdown @@ -31,4 +31,4 @@ Configuration variables: - **username** (*Required*: The username of an user with administrative privileges, usually *admin*. - **password** (*Required*): The password for your given admin account. -See the [device tracker component page](/components/device_tracker.html) for instructions how to configure the people to be tracked. +See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked. diff --git a/source/_components/device_tracker.luci.markdown b/source/_components/device_tracker.luci.markdown index 84becfbaba0..06b276c7d17 100644 --- a/source/_components/device_tracker.luci.markdown +++ b/source/_components/device_tracker.luci.markdown @@ -11,7 +11,7 @@ logo: openwrt.png ha_category: Presence Detection --- -_This is one of the two ways we support OpenWRT. If you encounter problems, try [ubus](/components/device_tracker.ubus.html)._ +_This is one of the two ways we support OpenWRT. If you encounter problems, try [ubus](/components/device_tracker.ubus/)._ This is a presence detection scanner for OpenWRT using [luci](http://wiki.openwrt.org/doc/techref/luci). @@ -36,4 +36,4 @@ Configuration variables: - **username** (*Required*): The username of an user with administrative privileges, usually *admin*. - **password** (*Required*): The password for your given admin account. -See the [device tracker component page](/components/device_tracker.html) for instructions how to configure the people to be tracked. +See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked. diff --git a/source/_components/device_tracker.markdown b/source/_components/device_tracker.markdown index 171c80ff43f..e5b5c81da5f 100644 --- a/source/_components/device_tracker.markdown +++ b/source/_components/device_tracker.markdown @@ -11,7 +11,7 @@ footer: true Home Assistant can get information from your wireless router to track which devices are connected. Please check the sidebar for a list of brands of supported wireless routers. -There are also trackers available which uses different technologies like [MQTT](/components/mqtt.html) or [nmap](/components/device_tracker.nmap_scanner.html) to scan the network for devices +There are also trackers available which uses different technologies like [MQTT](/components/mqtt/) or [nmap](/components/device_tracker.nmap_scanner/) to scan the network for devices To get started add the following lines to your `configuration.yaml` (example for Netgear): diff --git a/source/_components/device_tracker.netgear.markdown b/source/_components/device_tracker.netgear.markdown index a35a4c58509..bdad7e7ca38 100644 --- a/source/_components/device_tracker.netgear.markdown +++ b/source/_components/device_tracker.netgear.markdown @@ -29,4 +29,4 @@ Configuration variables: - **username** (*Required*: The username of an user with administrative privileges, usually *admin*. - **password** (*Required*): The password for your given admin account. -See the [device tracker component page](/components/device_tracker.html) for instructions how to configure the people to be tracked. +See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked. diff --git a/source/_components/device_tracker.nmap_scanner.markdown b/source/_components/device_tracker.nmap_scanner.markdown index 6bfeddd0c1a..bdee0d2da9e 100644 --- a/source/_components/device_tracker.nmap_scanner.markdown +++ b/source/_components/device_tracker.nmap_scanner.markdown @@ -30,5 +30,5 @@ device_tracker: `home_interval` is an optional value set in minutes. This will be the number of minutes nmap will not scan this device, assuming it is home, in order to preserve the device battery. -See the [device tracker component page](/components/device_tracker.html) for instructions how to +See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked. diff --git a/source/_components/device_tracker.owntracks.markdown b/source/_components/device_tracker.owntracks.markdown index 60778ff9cd5..4ba7cbd9ef5 100644 --- a/source/_components/device_tracker.owntracks.markdown +++ b/source/_components/device_tracker.owntracks.markdown @@ -17,8 +17,8 @@ This platform allows you to detect presence using [Owntracks](http://owntracks.o users to track their location on Android and iOS phones and publish it to an MQTT broker. This platform will connect to the broker and monitor for new locations. -This component requires [the MQTT component](/components/mqtt.html) to be set up and works very well -together with [the zone component](/components/zone.html). +This component requires [the MQTT component](/components/mqtt/) to be set up and works very well +together with [the zone component](/components/zone/). To integrate Owntracks in Home Assistant, add the following section to your `configuration.yaml` file: diff --git a/source/_components/device_tracker.snmp.markdown b/source/_components/device_tracker.snmp.markdown index 65d6f09c7a3..367041fbf8c 100644 --- a/source/_components/device_tracker.snmp.markdown +++ b/source/_components/device_tracker.snmp.markdown @@ -39,4 +39,4 @@ Configuration variables: - **baseoid** (*Required*): The OID prefix where wireless client registrations can be found, usually vendor specific. It's advised to use the numerical notation. To find this base OID, check vendor documentation or check the MIB file for your device. -See the [device tracker component page](/components/device_tracker.html) for instructions how to configure the people to be tracked. +See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked. diff --git a/source/_components/device_tracker.thomson.markdown b/source/_components/device_tracker.thomson.markdown index 6d640b9deb9..7847240d4b3 100644 --- a/source/_components/device_tracker.thomson.markdown +++ b/source/_components/device_tracker.thomson.markdown @@ -31,4 +31,4 @@ Configuration variables: - **username** (*Required*: The username of an user with administrative privileges, usually *admin*. - **password** (*Required*): The password for your given admin account. -See the [device tracker component page](/components/device_tracker.html) for instructions how to configure the people to be tracked. +See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked. diff --git a/source/_components/device_tracker.tomato.markdown b/source/_components/device_tracker.tomato.markdown index 886fd5ca88f..7f33d06d52e 100644 --- a/source/_components/device_tracker.tomato.markdown +++ b/source/_components/device_tracker.tomato.markdown @@ -30,4 +30,4 @@ Configuration variables: - **password** (*Required*): The password for your given admin account. - **http_id** (*Required*): The value can be obtained by logging in to the Tomato admin interface and search for `http_id` in the page source code. -See the [device tracker component page](/components/device_tracker.html) for instructions how to configure the people to be tracked. +See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked. diff --git a/source/_components/device_tracker.tplink.markdown b/source/_components/device_tracker.tplink.markdown index 5bae2e37865..a95022d65a2 100644 --- a/source/_components/device_tracker.tplink.markdown +++ b/source/_components/device_tracker.tplink.markdown @@ -38,4 +38,4 @@ For Archer C9 models running firmware version 150811 or later please use the enc 5. Type ```document.getElementById("login-password").value;```. 6. Copy the returned value to your Home Assistant configuration as password. -See the [device tracker component page](/components/device_tracker.html) for instructions how to configure the people to be tracked. +See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked. diff --git a/source/_components/device_tracker.ubus.markdown b/source/_components/device_tracker.ubus.markdown index 42543fa4ad7..0847e358630 100644 --- a/source/_components/device_tracker.ubus.markdown +++ b/source/_components/device_tracker.ubus.markdown @@ -11,7 +11,7 @@ logo: openwrt.png ha_category: Presence Detection --- -_This is one of the two ways we support OpenWRT. If you encounter problems, try [luci](/components/device_tracker.luci.html)._ +_This is one of the two ways we support OpenWRT. If you encounter problems, try [luci](/components/device_tracker.luci/)._ This is a presence detection scanner for OpenWRT using [ubus](http://wiki.openwrt.org/doc/techref/ubus). @@ -55,4 +55,4 @@ Configuration variables: - **username** (*Required*): The username of an user with administrative privileges, usually *admin*. - **password** (*Required*): The password for your given admin account. -See the [device tracker component page](/components/device_tracker.html) for instructions how to configure the people to be tracked. +See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked. diff --git a/source/_components/discovery.markdown b/source/_components/discovery.markdown index 0f490ffce1e..45ff84806ca 100644 --- a/source/_components/discovery.markdown +++ b/source/_components/discovery.markdown @@ -28,7 +28,7 @@ To load this component, add the following lines to your `configuration.yaml`: discovery: ``` -If you are developing a new platform, please read [how to make your platform discoverable]({{site_root}}/developers/add_new_platform.html#discovery). +If you are developing a new platform, please read [how to make your platform discoverable]({{site_root}}/developers/add_new_platform/#discovery).

There is currently a known issue with running this playform on a 64-bit version of Python. diff --git a/source/_components/ifttt.manything.markdown b/source/_components/ifttt.manything.markdown index 77a295be55b..e59ccac1ed7 100644 --- a/source/_components/ifttt.manything.markdown +++ b/source/_components/ifttt.manything.markdown @@ -15,7 +15,7 @@ ha_category: Camera camera for monitoring your home, your pets, anything! Comes with live streaming, motion activated alerts, cloud video recording, and more. To get manything support, HA will use IFTTT's [Maker Channel](https://ifttt.com/maker) and the [ManyThing Channel](https://ifttt.com/manything). -Use the [IFTTT Setup instructions](/components/ifttt.html) to activate the IFTTT Platform. +Use the [IFTTT Setup instructions](/components/ifttt/) to activate the IFTTT Platform. After setting up IFTTT, Maker Channel and ManyThing Channel, you can use the following examples to configure Home Assistant. diff --git a/source/_components/ifttt.markdown b/source/_components/ifttt.markdown index 27d9c4cce0e..97ce8c5876d 100644 --- a/source/_components/ifttt.markdown +++ b/source/_components/ifttt.markdown @@ -76,4 +76,4 @@ Additional examples of using IFTTT channels can be found below. Channel | Description ----- | ----- -[Manything](/components/ifttt.manything.html) | Automates turning recording ON and OFF based on Home Assistant AWAY and HOME values. +[Manything](/components/ifttt.manything/) | Automates turning recording ON and OFF based on Home Assistant AWAY and HOME values. diff --git a/source/_components/light.hue.markdown b/source/_components/light.hue.markdown index 5622d1aa5e1..3ba5156cb5d 100644 --- a/source/_components/light.hue.markdown +++ b/source/_components/light.hue.markdown @@ -14,7 +14,7 @@ featured: true -Philips Hue support is integrated into Home Assistant as a light platform. The preferred way to setup the Philips Hue platform is by enabling the [the discovery component]({{site_root}}/components/discovery.html). +Philips Hue support is integrated into Home Assistant as a light platform. The preferred way to setup the Philips Hue platform is by enabling the [the discovery component]({{site_root}}/components/discovery/). If you want to enable the light component directly, add the following lines to your `configuration.yaml`: diff --git a/source/_components/light.markdown b/source/_components/light.markdown index 0c3f44c2d1b..f9eeb35758c 100644 --- a/source/_components/light.markdown +++ b/source/_components/light.markdown @@ -18,7 +18,7 @@ It supports the following platforms: * `hue` for Philips Hue * `wink` for Wink -Preferred way to setup the Philips Hue platform is through the [the discovery component]({{site_root}}/components/discovery.html). For the Wink light platform enable [the wink component]({{site_root}}/components/wink.html). +Preferred way to setup the Philips Hue platform is through the [the discovery component]({{site_root}}/components/discovery/). For the Wink light platform enable [the wink component]({{site_root}}/components/wink/). If you want to enable the light component directly, add the following lines to your `configuration.yaml`: @@ -33,7 +33,7 @@ The light component supports multiple entries in configuration.yaml ### Service `light.turn_on` -Turns one light on or multiple lights on using [groups]({{site_root}}/components/group.html). +Turns one light on or multiple lights on using [groups]({{site_root}}/components/group/). | Service data attribute | Optional | Description | | ---------------------- | -------- | ----------- | diff --git a/source/_components/light.wink.markdown b/source/_components/light.wink.markdown index 9f12c36a2e8..d4d86298a7e 100644 --- a/source/_components/light.wink.markdown +++ b/source/_components/light.wink.markdown @@ -14,4 +14,4 @@ ha_category: Light The wink sensor platform allows you to use your [Wink](http://www.wink.com/) lights. -The requirement is that you have setup your [Wink hub](/components/light.wink.html). +The requirement is that you have setup your [Wink hub](/components/light.wink/). diff --git a/source/_components/media_player.cast.markdown b/source/_components/media_player.cast.markdown index 139bb179e63..89383e36cd7 100644 --- a/source/_components/media_player.cast.markdown +++ b/source/_components/media_player.cast.markdown @@ -13,7 +13,7 @@ featured: true --- -Google Cast devices will be automatically discovered if you enable [the discovery component]({{site_root}}/components/discovery.html). There is a issue where Chromecasts can only be discovered if your device is connected to the same subnet as your Chromecast. +Google Cast devices will be automatically discovered if you enable [the discovery component]({{site_root}}/components/discovery/). There is a issue where Chromecasts can only be discovered if your device is connected to the same subnet as your Chromecast. Chromecast platform can also be forced to load by adding the following lines to your `configuration.yaml`: diff --git a/source/_components/media_player.plex.markdown b/source/_components/media_player.plex.markdown index 4c98446e10b..f2e319f726f 100644 --- a/source/_components/media_player.plex.markdown +++ b/source/_components/media_player.plex.markdown @@ -14,7 +14,7 @@ featured: true The Plex platform allows you to connect a [Plex Media Server](https://plex.tv) to Home Assistant. It will allow you to control media playback and see the current playing item. -The preferred way to setup the Plex platform is by enabling the the [the discovery component]({{site_root}}/components/discovery.html) and requires GDM to be enabled. +The preferred way to setup the Plex platform is by enabling the the [the discovery component]({{site_root}}/components/discovery/) and requires GDM to be enabled. If local authentication is enabled or multiple users are defined, HASS requires an authentication token to be entered in the webinterface. See Finding your account token / X-Plex-Token. diff --git a/source/_components/modbus.markdown b/source/_components/modbus.markdown index 0d5b3da93e7..fa1fdabcb5e 100644 --- a/source/_components/modbus.markdown +++ b/source/_components/modbus.markdown @@ -57,6 +57,6 @@ Configuration variables: ## {% linkable_title Building on top of Modbus %} - - [Modbus Sensor](/components/sensor.modbus.html) - - [Modbus Switch](/components/switch.modbus.html) + - [Modbus Sensor](/components/sensor.modbus/) + - [Modbus Switch](/components/switch.modbus/) diff --git a/source/_components/mqtt.markdown b/source/_components/mqtt.markdown index fea71e1ed41..2d9ff6688da 100644 --- a/source/_components/mqtt.markdown +++ b/source/_components/mqtt.markdown @@ -82,7 +82,7 @@ mqtt: [CloudMQTT](https://www.cloudmqtt.com) is a hosted private MQTT instance that is free up to 10 connected devices. This is enough to get started with for example -[OwnTracks](/components/device_tracker.owntracks.html) and give you a taste of what is possible. +[OwnTracks](/components/device_tracker.owntracks/) and give you a taste of what is possible.

Home Assistant is not affiliated with CloudMQTT nor will receive any kickbacks. @@ -112,12 +112,12 @@ of CloudMQTT (port range 20 000 - 30 000). ## {% linkable_title Building on top of MQTT %} - - [MQTT Sensor](/components/sensor.mqtt.html) - - [MQTT Switch](/components/switch.mqtt.html) - - [MQTT Device Tracker](/components/device_tracker.mqtt.html) - - [OwnTracks Device Tracker](/components/device_tracker.owntracks.html) - - [MQTT automation rule](/components/automation.html#mqtt-based-automation) - - [MQTT alarm](/components/alarm_control_panel.mqtt.html) + - [MQTT Sensor](/components/sensor.mqtt/) + - [MQTT Switch](/components/switch.mqtt/) + - [MQTT Device Tracker](/components/device_tracker.mqtt/) + - [OwnTracks Device Tracker](/components/device_tracker.owntracks/) + - [MQTT automation rule](/components/automation/#mqtt-based-automation) + - [MQTT alarm](/components/alarm_control_panel.mqtt/) - Integrating it into a component. See the [MQTT example component](https://github.com/balloob/home-assistant/blob/dev/config/custom_components/mqtt_example.py) how to do this. ## {% linkable_title Testing your setup %} diff --git a/source/_components/notify.file.markdown b/source/_components/notify.file.markdown index 2d8a38208cf..da02630853f 100644 --- a/source/_components/notify.file.markdown +++ b/source/_components/notify.file.markdown @@ -30,4 +30,4 @@ Configuration variables: - **filename** (*Required*): Name of the file to use. The file will be created if it doesn't exist and saved in your `config/` folder. - **timestamp** (*Optional*): Setting `timestamp` to 1 adds a timestamp to every entry. -To use notifications, please see the [getting started with automation page]({{site_root}}/components/automation.html). +To use notifications, please see the [getting started with automation page]({{site_root}}/components/automation/). diff --git a/source/_components/notify.instapush.markdown b/source/_components/notify.instapush.markdown index 238d1bad05c..9160a0ea649 100644 --- a/source/_components/notify.instapush.markdown +++ b/source/_components/notify.instapush.markdown @@ -49,4 +49,4 @@ curl -X POST \ ``` For further details, please check the [API](https://instapush.im/developer/rest). -To use notifications, please see the [getting started with automation page]({{site_root}}/components/automation.html). +To use notifications, please see the [getting started with automation page]({{site_root}}/components/automation/). diff --git a/source/_components/notify.markdown b/source/_components/notify.markdown index eecd3eccf7f..abc80e8631c 100644 --- a/source/_components/notify.markdown +++ b/source/_components/notify.markdown @@ -40,4 +40,4 @@ automation: service_data: {"message":"YAY"} ``` -For more automation examples, see the [getting started with automation page]({{site_root}}/components/automation.html). +For more automation examples, see the [getting started with automation page]({{site_root}}/components/automation/). diff --git a/source/_components/notify.nma.markdown b/source/_components/notify.nma.markdown index 69f1a4bff81..ccd634f28c7 100644 --- a/source/_components/notify.nma.markdown +++ b/source/_components/notify.nma.markdown @@ -31,4 +31,4 @@ Configuration variables: Details for the API : https://www.notifymyandroid.com/api.jsp -To use notifications, please see the [getting started with automation page]({{site_root}}/components/automation.html). +To use notifications, please see the [getting started with automation page]({{site_root}}/components/automation/). diff --git a/source/_components/notify.pushbullet.markdown b/source/_components/notify.pushbullet.markdown index 87e73452448..5e1ae322e9b 100644 --- a/source/_components/notify.pushbullet.markdown +++ b/source/_components/notify.pushbullet.markdown @@ -30,4 +30,4 @@ Configuration variables: - **name** (*Optional*): Setting the optional parameter `name` allows multiple notifiers to be created. The default value is `notify`. The notifier will bind to the service `notify.NOTIFIER_NAME`. - **api_key** (*Required*): Enter the API key for PushBullet. Go to https://www.pushbullet.com/ to retrieve your API key. -For more automation examples, see the [getting started with automation page]({{site_root}}/components/automation.html). +For more automation examples, see the [getting started with automation page]({{site_root}}/components/automation/). diff --git a/source/_components/notify.pushover.markdown b/source/_components/notify.pushover.markdown index 0a76bf6e0c1..0ce601da210 100644 --- a/source/_components/notify.pushover.markdown +++ b/source/_components/notify.pushover.markdown @@ -36,5 +36,5 @@ This is a quote from the pushover website regarding free/open source apps: When setting up the application you can use this [icon](https://home-assistant.io/images/favicon-192x192.png). -For more automation examples, see the [getting started with automation page]({{site_root}}/components/automation.html). +For more automation examples, see the [getting started with automation page]({{site_root}}/components/automation/). diff --git a/source/_components/notify.slack.markdown b/source/_components/notify.slack.markdown index f4e75c5d621..df0d51888e0 100644 --- a/source/_components/notify.slack.markdown +++ b/source/_components/notify.slack.markdown @@ -33,5 +33,5 @@ Configuration variables: - **api_key** (*Required*): The slack API token to use for sending slack messages. You can get your slack API token here https://api.slack.com/web?sudo=1 - **default_channel** (*Required*): The default channel to post to if no channel is explicitly specified when sending the notification message. -To use notifications, please see the [getting started with automation page]({{site_root}}/components/automation.html). +To use notifications, please see the [getting started with automation page]({{site_root}}/components/automation/). diff --git a/source/_components/notify.smtp.markdown b/source/_components/notify.smtp.markdown index 17ec4056024..f90671994fc 100644 --- a/source/_components/notify.smtp.markdown +++ b/source/_components/notify.smtp.markdown @@ -51,4 +51,4 @@ Keep in mind that if the password contains a colon, it needs to be wrapped in ap For Google Mail (smtp.gmail.com) an additional step in the setup process is needed. Google has some extra layers of protection which need special attention. By default, the usage by external applications, especially scripts, is limited. Visit the [Less secure apps](https://www.google.com/settings/security/lesssecureapps) page and enable it. -To use notifications, please see the [getting started with automation page]({{site_root}}/components/automation.html). +To use notifications, please see the [getting started with automation page]({{site_root}}/components/automation/). diff --git a/source/_components/notify.syslog.markdown b/source/_components/notify.syslog.markdown index e4dc1e0bd8d..9ff602d809c 100644 --- a/source/_components/notify.syslog.markdown +++ b/source/_components/notify.syslog.markdown @@ -57,4 +57,4 @@ The table contains values to use in your `configuration.yaml` file. For details about facility, option, and priority please consult the [wikpedia article](http://en.wikipedia.org/wiki/Syslog) and [RFC 3164](http://tools.ietf.org/html/rfc3164). -To use notifications, please see the [getting started with automation page]({{site_root}}/components/automation.html). +To use notifications, please see the [getting started with automation page]({{site_root}}/components/automation/). diff --git a/source/_components/notify.telegram.markdown b/source/_components/notify.telegram.markdown index 4be8021609a..3f963cbc011 100644 --- a/source/_components/notify.telegram.markdown +++ b/source/_components/notify.telegram.markdown @@ -48,4 +48,4 @@ The default value is `notify`. The notifier will bind to the service - **api_key** (*Required*): The API token of your bot. - **chat_id** (*Required*: The chat ID of your user. -To use notifications, please see the [getting started with automation page]({{site_root}}/components/automation.html). +To use notifications, please see the [getting started with automation page]({{site_root}}/components/automation/). diff --git a/source/_components/notify.xmpp.markdown b/source/_components/notify.xmpp.markdown index 258c9b97be6..d381fd0fca1 100644 --- a/source/_components/notify.xmpp.markdown +++ b/source/_components/notify.xmpp.markdown @@ -34,4 +34,4 @@ Configuration variables: All Jabber IDs (JID) must include the domain. Make sure that the password matches the account provided as sender. -To use notifications, please see the [getting started with automation page]({{site_root}}/components/automation.html). +To use notifications, please see the [getting started with automation page]({{site_root}}/components/automation/). diff --git a/source/_components/sensor.command_sensor.markdown b/source/_components/sensor.command_sensor.markdown index 0255f920356..66eee729462 100644 --- a/source/_components/sensor.command_sensor.markdown +++ b/source/_components/sensor.command_sensor.markdown @@ -75,7 +75,7 @@ The `correction_factor` will make sure that the value is shown in a useful forma ### {% linkable_title Use an external script %} -The example is doing the same as the [aREST sensor](/components/sensor.arest.html) but with an external Python script. It should give you an idea about interacting with devices which are exposing a RESTful API. +The example is doing the same as the [aREST sensor](/components/sensor.arest/) but with an external Python script. It should give you an idea about interacting with devices which are exposing a RESTful API. The one-line script to retrieve a value is shown below. Of course would it be possible to use this directly in the `configuration.yaml` file but need extra care about the quotation marks. diff --git a/source/_components/sensor.rest.markdown b/source/_components/sensor.rest.markdown index fd8801af944..5418981fff9 100644 --- a/source/_components/sensor.rest.markdown +++ b/source/_components/sensor.rest.markdown @@ -86,7 +86,7 @@ To display the IP address, the entry for a sensor in the `configuration.yaml` fi ### {% linkable_title Single value from a local Glances instance %} -The [glances](/components/sensor.glances.html) sensor is doing the exact same thing for all exposed values. +The [glances](/components/sensor.glances/) sensor is doing the exact same thing for all exposed values. Add something similar to the entry below to your `configuration.yaml` file: diff --git a/source/_components/sensor.wink.markdown b/source/_components/sensor.wink.markdown index a44bef59345..5238e0d8cdc 100644 --- a/source/_components/sensor.wink.markdown +++ b/source/_components/sensor.wink.markdown @@ -14,5 +14,5 @@ ha_category: Sensor The wink sensor platform allows you to get data from your [Wink](http://www.wink.com/) sensors. -The requirement is that you have setup your [Wink hub](/components/light.wink.html). +The requirement is that you have setup your [Wink hub](/components/light.wink/). diff --git a/source/_components/simple_alarm.markdown b/source/_components/simple_alarm.markdown index 9590158f08a..726d3edea2e 100644 --- a/source/_components/simple_alarm.markdown +++ b/source/_components/simple_alarm.markdown @@ -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: diff --git a/source/_components/sun.markdown b/source/_components/sun.markdown index 3dd6b29b5ff..98770e33731 100644 --- a/source/_components/sun.markdown +++ b/source/_components/sun.markdown @@ -14,7 +14,7 @@ ha_category: Weather The `sun` component will use your current location to track if the sun is above or below the horizon. The sun can be used within automation as [a trigger with an optional offset to simulate dawn/dusk][automation-trigger]. -[automation-trigger]: /components/automation.html#sun-trigger +[automation-trigger]: /components/automation/#sun-trigger ```yaml # Example configuration.yaml entry diff --git a/source/_components/switch.command_switch.markdown b/source/_components/switch.command_switch.markdown index cb6bbf04608..f8282a19767 100644 --- a/source/_components/switch.command_switch.markdown +++ b/source/_components/switch.command_switch.markdown @@ -38,7 +38,7 @@ In this section you find some real life examples of how to use this switch. ### {% linkable_title aREST device %} -The example below is doing the same as the [aREST switch](/components/switch.arest.html). The commandline tool `[curl](http://curl.haxx.se/)` is used to toogle a pin which is controllable through REST. +The example below is doing the same as the [aREST switch](/components/switch.arest/). The commandline tool `[curl](http://curl.haxx.se/)` is used to toogle a pin which is controllable through REST. ```yaml # Example configuration.yaml entry diff --git a/source/_components/switch.wink.markdown b/source/_components/switch.wink.markdown index f24ef16fb8c..29ca5b82106 100644 --- a/source/_components/switch.wink.markdown +++ b/source/_components/switch.wink.markdown @@ -14,5 +14,5 @@ ha_category: Switch The wink switch platform allows you to control your [Wink](http://www.wink.com/) switches. -The requirement is that you have setup your [Wink hub](/components/light.wink.html). +The requirement is that you have setup your [Wink hub](/components/light.wink/). diff --git a/source/_components/vera.markdown b/source/_components/vera.markdown index 51a98d5ffd3..4ceee75d400 100644 --- a/source/_components/vera.markdown +++ b/source/_components/vera.markdown @@ -16,6 +16,6 @@ The [Vera](http://getvera.com) ecosystem is using Z-Wave for communication betwe ## {% linkable_title Building on top of Vera %} - - [Vera Sensor](/components/sensor.vera.html) - - [Vera Switch](/components/switch.vera.html) - - [Vera Light](/components/light.vera.html) + - [Vera Sensor](/components/sensor.vera/) + - [Vera Switch](/components/switch.vera/) + - [Vera Light](/components/light.vera/) diff --git a/source/_components/zone.markdown b/source/_components/zone.markdown index 9a0674113f0..7cb36f455f8 100644 --- a/source/_components/zone.markdown +++ b/source/_components/zone.markdown @@ -12,7 +12,7 @@ ha_category: Organization Zones allow you to specify certain regions on earth (for now). When a device tracker sees a device to be within a zone, the state will take the name from the zone. Zones can also be used as a -[trigger](/components/automation.html#zone-trigger) or [condition](/components/automation.html#zone-condition) +[trigger](/components/automation/#zone-trigger) or [condition](/components/automation/#zone-condition) inside automation setups. Zones support the usual method to specify multiple zones, use keys `zone:`, `zone 2:` etc. diff --git a/source/_cookbook/automation_for_rainy_days.markdown b/source/_cookbook/automation_for_rainy_days.markdown index 8af1d009292..1fc64a1a03d 100644 --- a/source/_cookbook/automation_for_rainy_days.markdown +++ b/source/_cookbook/automation_for_rainy_days.markdown @@ -11,7 +11,7 @@ footer: true ### 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. diff --git a/source/_includes/asides/component_navigation.html b/source/_includes/asides/component_navigation.html index e61ff281e44..2ff27e24935 100644 --- a/source/_includes/asides/component_navigation.html +++ b/source/_includes/asides/component_navigation.html @@ -11,7 +11,7 @@ {% assign is_platform = true %} {% assign imp_name = file_parts[1] %} {% 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 %} {% else %} {% assign is_platform = false %} diff --git a/source/_includes/custom/grid_item_left.html b/source/_includes/custom/grid_item_left.html index c4ea1b9a922..c756f093443 100644 --- a/source/_includes/custom/grid_item_left.html +++ b/source/_includes/custom/grid_item_left.html @@ -2,46 +2,46 @@

Home Assistant will track the state of all the devices in your home, so you don't have to.

- + - + - + - + - + - + - + - + - + - + - + - + - + - +
diff --git a/source/_includes/custom/navigation.html b/source/_includes/custom/navigation.html index 4d9eac4af00..5da7853c2e5 100644 --- a/source/_includes/custom/navigation.html +++ b/source/_includes/custom/navigation.html @@ -3,10 +3,10 @@ Getting started @@ -14,16 +14,16 @@
  • Developers
  • Blog
    • diff --git a/source/_posts/2015-01-11-bootstrapping-your-setup-with-discovery.markdown b/source/_posts/2015-01-11-bootstrapping-your-setup-with-discovery.markdown index 9c673720a09..6f1f1a03fa4 100644 --- a/source/_posts/2015-01-11-bootstrapping-your-setup-with-discovery.markdown +++ b/source/_posts/2015-01-11-bootstrapping-your-setup-with-discovery.markdown @@ -20,4 +20,4 @@ To enable the discovery component, add the following to your `home-assistant.con [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. diff --git a/source/_posts/2015-02-24-streaming-updates.markdown b/source/_posts/2015-02-24-streaming-updates.markdown index 8385fc10999..5be909ceeca 100644 --- a/source/_posts/2015-02-24-streaming-updates.markdown +++ b/source/_posts/2015-02-24-streaming-updates.markdown @@ -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. -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: diff --git a/source/_posts/2015-04-25-release-notes.markdown b/source/_posts/2015-04-25-release-notes.markdown index 36fa309a29c..85091861e86 100644 --- a/source/_posts/2015-04-25-release-notes.markdown +++ b/source/_posts/2015-04-25-release-notes.markdown @@ -21,7 +21,7 @@ __ISY994 hub support__
    [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 # Example configuration.yaml entry diff --git a/source/_posts/2015-06-10-release-notes.markdown b/source/_posts/2015-06-10-release-notes.markdown index 8f4f82bef1e..985eba9c910 100644 --- a/source/_posts/2015-06-10-release-notes.markdown +++ b/source/_posts/2015-06-10-release-notes.markdown @@ -145,7 +145,7 @@ notify: __Swiss Public transport sensor__
    -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__
    diff --git a/source/_posts/2015-07-11-ip-cameras-arduino-kodi-efergy-support.markdown b/source/_posts/2015-07-11-ip-cameras-arduino-kodi-efergy-support.markdown index 711c72a21f8..fef996e3e1d 100644 --- a/source/_posts/2015-07-11-ip-cameras-arduino-kodi-efergy-support.markdown +++ b/source/_posts/2015-07-11-ip-cameras-arduino-kodi-efergy-support.markdown @@ -35,7 +35,7 @@ To update to the latest version, run scripts/update. Please report __Arduino__
    -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 # Example configuration.yaml entry diff --git a/source/_posts/2015-08-09-mqtt-raspberry-pi-squeezebox-asuswrt-support.markdown b/source/_posts/2015-08-09-mqtt-raspberry-pi-squeezebox-asuswrt-support.markdown index 5591d5e4506..18710bdafbc 100644 --- a/source/_posts/2015-08-09-mqtt-raspberry-pi-squeezebox-asuswrt-support.markdown +++ b/source/_posts/2015-08-09-mqtt-raspberry-pi-squeezebox-asuswrt-support.markdown @@ -15,8 +15,8 @@ __MQTT Support__
    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-automation]: /components/automation.html#mqtt-based-automation -[mqtt-component]: /components/mqtt.html +[mqtt-automation]: /components/automation/#mqtt-based-automation +[mqtt-component]: /components/mqtt/ ```yaml # Example configuration.yaml entry diff --git a/source/_posts/2015-08-26-laundry-automation-with-moteino-mqtt-and-home-assistant.markdown b/source/_posts/2015-08-26-laundry-automation-with-moteino-mqtt-and-home-assistant.markdown index a2e4e564ec5..80fd3206ed3 100644 --- a/source/_posts/2015-08-26-laundry-automation-with-moteino-mqtt-and-home-assistant.markdown +++ b/source/_posts/2015-08-26-laundry-automation-with-moteino-mqtt-and-home-assistant.markdown @@ -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. -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. @@ -27,14 +27,14 @@ After taking some sample data from the accelerometers while each appliance was i -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.

    Status of the dryer and washer in Home Assistant

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

    diff --git a/source/_posts/2015-08-31-version-7-revamped-ui-and-improved-distribution.markdown b/source/_posts/2015-08-31-version-7-revamped-ui-and-improved-distribution.markdown index 0a4faf3a035..c22d422060c 100644 --- a/source/_posts/2015-08-31-version-7-revamped-ui-and-improved-distribution.markdown +++ b/source/_posts/2015-08-31-version-7-revamped-ui-and-improved-distribution.markdown @@ -73,8 +73,8 @@ __MQTT Sensors and Switches__
    integration with MQTTT: [sensor][mqtt-sensor] and [switch][mqtt-switch]. Both platforms require the MQTT component to be connected to a broker. -[mqtt-sensor]: /components/sensor.mqtt.html -[mqtt-switch]: /components/switch.mqtt.html +[mqtt-sensor]: /components/sensor.mqtt/ +[mqtt-switch]: /components/switch.mqtt/ ```yaml # Example configuration.yml entr diff --git a/source/_posts/2015-09-11-different-ways-to-use-mqtt-with-home-assistant.markdown b/source/_posts/2015-09-11-different-ways-to-use-mqtt-with-home-assistant.markdown index 49f336d48a9..e7806bd8097 100644 --- a/source/_posts/2015-09-11-different-ways-to-use-mqtt-with-home-assistant.markdown +++ b/source/_posts/2015-09-11-different-ways-to-use-mqtt-with-home-assistant.markdown @@ -11,7 +11,7 @@ og_image: /images/blog/2015-09-mqtt/arduino.png --- -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. @@ -32,7 +32,7 @@ sensor: 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. diff --git a/source/_posts/2015-09-13-home-assistant-meets-ifttt.markdown b/source/_posts/2015-09-13-home-assistant-meets-ifttt.markdown index 636d75209c1..e5d27400333 100644 --- a/source/_posts/2015-09-13-home-assistant-meets-ifttt.markdown +++ b/source/_posts/2015-09-13-home-assistant-meets-ifttt.markdown @@ -25,7 +25,7 @@ if your smoke alarm goes off.

    -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. diff --git a/source/_posts/2015-09-18-monitoring-with-glances-and-home-assistant.markdown b/source/_posts/2015-09-18-monitoring-with-glances-and-home-assistant.markdown index 52853449ad8..59e7499be26 100644 --- a/source/_posts/2015-09-18-monitoring-with-glances-and-home-assistant.markdown +++ b/source/_posts/2015-09-18-monitoring-with-glances-and-home-assistant.markdown @@ -11,13 +11,13 @@ og_image: /images/supported_brands/glances.png --- -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. 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. @@ -55,7 +55,7 @@ curl -X GET http://IP_ADDRESS:61208/api/2/mem/used {"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 # Example configuration.yaml entry diff --git a/source/_posts/2015-09-19-alarm-sonos-and-itunes-support.markdown b/source/_posts/2015-09-19-alarm-sonos-and-itunes-support.markdown index 462dc8f0812..f10625982b0 100644 --- a/source/_posts/2015-09-19-alarm-sonos-and-itunes-support.markdown +++ b/source/_posts/2015-09-19-alarm-sonos-and-itunes-support.markdown @@ -42,7 +42,7 @@ media_player: __Automation__
    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 -[getting started with automation](/getting-started/automation.html) page. +[getting started with automation](/getting-started/automation/) page. ```yaml # Example of entry in configuration.yaml diff --git a/source/_posts/2015-10-05-home-assistant-goes-geo-with-owntracks.markdown b/source/_posts/2015-10-05-home-assistant-goes-geo-with-owntracks.markdown index ba6f57cd781..e7581bf807b 100644 --- a/source/_posts/2015-10-05-home-assistant-goes-geo-with-owntracks.markdown +++ b/source/_posts/2015-10-05-home-assistant-goes-geo-with-owntracks.markdown @@ -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. -[platform-owntracks]: /components/device_tracker.owntracks.html -[component-zone]: /components/zone.html -[zone-automation]: /components/automation.html#zone-trigger -[start-presence]: /getting-started/presence-detection.html +[platform-owntracks]: /components/device_tracker.owntracks/ +[component-zone]: /components/zone/ +[zone-automation]: /components/automation/#zone-trigger +[start-presence]: /getting-started/presence-detection/

    @@ -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 short summary of highlights: - + - - Sensor: [rest platform](/components/sensor.rest.html) added ([@fabaff](https://github.com/fabaff)) - - Alarm Control Panel: [MQTT platform](/components/alarm_control_panel.mqtt.html) 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)) + - Sensor: [rest platform](/components/sensor.rest/) added ([@fabaff](https://github.com/fabaff)) + - Alarm Control Panel: [MQTT platform](/components/alarm_control_panel.mqtt/) added ([@sfam](https://github.com/sfam)) + - 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)) - 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)) - Scene support for media player ([@maddox](https://github.com/maddox)) diff --git a/source/_posts/2015-10-11-measure-temperature-with-esp8266-and-report-to-mqtt.markdown b/source/_posts/2015-10-11-measure-temperature-with-esp8266-and-report-to-mqtt.markdown index bea4341a47c..5cec10058dc 100644 --- a/source/_posts/2015-10-11-measure-temperature-with-esp8266-and-report-to-mqtt.markdown +++ b/source/_posts/2015-10-11-measure-temperature-with-esp8266-and-report-to-mqtt.markdown @@ -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 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, soldering iron + wire, Serial USB cable._ diff --git a/source/_posts/2015-10-11-rfxtrx-blinkstick-and-snmp-support.markdown b/source/_posts/2015-10-11-rfxtrx-blinkstick-and-snmp-support.markdown index 9e0365b0697..1b8197e8df1 100644 --- a/source/_posts/2015-10-11-rfxtrx-blinkstick-and-snmp-support.markdown +++ b/source/_posts/2015-10-11-rfxtrx-blinkstick-and-snmp-support.markdown @@ -20,11 +20,11 @@ This release also includes some new platforms (because they keep coming!): - - Light: [blinkstick platform](/components/light.blinksticklight.html) added ([@alanbowman](https://github.com/alanbowman)) - - Device Tracker: [SNMP platform](/components/device_tracker.snmp.html) added ([@tomduijf](https://github.com/tomduijf)) - - Light: [rfxtrx platform](/components/light.rfxtrx.html) added ([@badele](https://github.com/badele)) - - Switch: [rfxtrx platform](/components/switch.rfxtrx.html) added ([@badele](https://github.com/badele)) - - Notify: [telegram platform](/components/notify.telegram.html) added ([@fabaff](https://github.com/fabaff)) + - Light: [blinkstick platform](/components/light.blinksticklight/) added ([@alanbowman](https://github.com/alanbowman)) + - Device Tracker: [SNMP platform](/components/device_tracker.snmp/) added ([@tomduijf](https://github.com/tomduijf)) + - Light: [rfxtrx platform](/components/light.rfxtrx/) added ([@badele](https://github.com/badele)) + - Switch: [rfxtrx platform](/components/switch.rfxtrx/) added ([@badele](https://github.com/badele)) + - 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. -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/). diff --git a/source/_posts/2015-10-26-firetv-and-radiotherm-now-supported.markdown b/source/_posts/2015-10-26-firetv-and-radiotherm-now-supported.markdown index efc86bbfb18..90c3e8f15cd 100644 --- a/source/_posts/2015-10-26-firetv-and-radiotherm-now-supported.markdown +++ b/source/_posts/2015-10-26-firetv-and-radiotherm-now-supported.markdown @@ -21,22 +21,22 @@ complete revamp. - - Device tracker: Newer [TP-Link routers](/components/device_tracker.tplink.html) now supported ([@mKeRix](https://github.com/mKeRix)) - - Alarm Control Panel: [Manual alarm](/components/alarm_control_panel.manual.html) added ([@sfam](https://github.com/sfam)) - - Thermostat: [Radiotherm](/components/thermostat.radiotherm.html) now supported ([@toddeye](https://github.com/toddeye)) - - Media Player: [Amazon FireTV](/components/media_player.firetv.html) now supported ([@happyleavesaoc](https://github.com/happyleavesaoc)) - - Device Tracker: [Geofancy](/components/device_tracker.geofancy.html) 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)) - - [Scripts](/components/script.html) 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)) - - Sensor: [aRest](/components/sensor.arest.html) 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)) - - Thermostat: [Heat Control](/components/thermostat.heat_control.html) has been completely rewritten ([@balloob](https://github.com/balloob)) - - Switch: [Rest](/components/switch.rest.html) 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)) - - [Downloader](/components/downloader.html) will now treat relative paths based on config dir ([@tomduijf](https://github.com/tomduijf)) + - 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/) added ([@sfam](https://github.com/sfam)) + - Thermostat: [Radiotherm](/components/thermostat.radiotherm/) now supported ([@toddeye](https://github.com/toddeye)) + - Media Player: [Amazon FireTV](/components/media_player.firetv/) now supported ([@happyleavesaoc](https://github.com/happyleavesaoc)) + - Device Tracker: [Geofancy](/components/device_tracker.geofancy/) now supported ([@wind-rider](https://github.com/wind-rider)) + - New component [Shell Command](/components/shell_command/) can expose shell commands as services ([@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/) now supported ([@MakeMeASandwich](https://github.com/MakeMeASandwich)) + - Sensor: [aRest](/components/sensor.arest/) can now also read out pins ([@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/) has been completely rewritten ([@balloob](https://github.com/balloob)) + - Switch: [Rest](/components/switch.rest/) now supported ([@bachp](https://github.com/bachp)) + - Media Player: [Plex](/components/media_player.plex/) can now be auto discovered and configure itself ([@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)) - - 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)) @@ -45,11 +45,11 @@ complete revamp. As part of this release we did some cleanup which introduced backwards incompatible changes: **Heat Control thermostat no longer includes scheduling features.**
    -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. **Config changed for calling a service from a script.**
    -`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. **Scenes can no longer be turned off.**
    diff --git a/source/developers/add_new_platform.markdown b/source/developers/add_new_platform.markdown index ab4333b1681..fe2c2414f02 100644 --- a/source/developers/add_new_platform.markdown +++ b/source/developers/add_new_platform.markdown @@ -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. 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 %} diff --git a/source/developers/api.markdown b/source/developers/api.markdown index 777ce646f2c..e2a3fb24705 100644 --- a/source/developers/api.markdown +++ b/source/developers/api.markdown @@ -12,5 +12,5 @@ footer: true Home Assistant is offering a RESTful API and a Python API for convenient access to a Home Assistant instance over HTTP. -- [Rest API](/developers/rest_api.html) -- [Python API](/developers/python_api.html) +- [Rest API](/developers/rest_api/) +- [Python API](/developers/python_api/) diff --git a/source/developers/architecture.markdown b/source/developers/architecture.markdown index a01c95c5742..99ca5a1f297 100644 --- a/source/developers/architecture.markdown +++ b/source/developers/architecture.markdown @@ -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. -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 %} These components provide small pieces of home automation logic or services that do common tasks within your house. diff --git a/source/developers/frontend.markdown b/source/developers/frontend.markdown index 25196bc328c..64f7a696c1e 100644 --- a/source/developers/frontend.markdown +++ b/source/developers/frontend.markdown @@ -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`. * 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 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.

    diff --git a/source/developers/index.markdown b/source/developers/index.markdown index dcbb3c9451b..5e17dfea53f 100644 --- a/source/developers/index.markdown +++ b/source/developers/index.markdown @@ -51,10 +51,10 @@ requests. ### {% linkable_title Further reading %} -- [Home Assistant Architecture](/developers/architecture.html) -- [Frontend development](/developers/frontend.html) -- [Creating a custom component](/developers/creating_components.html) -- [Adding support for a new platform](/developers/add_new_platform.html) -- [Rest API](/developers/api.html) -- [Website](/developers/website.html) +- [Home Assistant Architecture](/developers/architecture/) +- [Frontend development](/developers/frontend/) +- [Creating a custom component](/developers/creating_components/) +- [Adding support for a new platform](/developers/add_new_platform/) +- [Rest API](/developers/api/) +- [Website](/developers/website/) diff --git a/source/developers/python_api.markdown b/source/developers/python_api.markdown index b3b2d43cf5d..06395eb10f5 100644 --- a/source/developers/python_api.markdown +++ b/source/developers/python_api.markdown @@ -9,7 +9,7 @@ sharing: 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. diff --git a/source/getting-started/automation.markdown b/source/getting-started/automation.markdown index 24ad1c8d5c7..88721783440 100644 --- a/source/getting-started/automation.markdown +++ b/source/getting-started/automation.markdown @@ -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 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 %} @@ -165,10 +165,10 @@ automation: We went over the basics of creating a home automation rule. From here no longer any hand holding, go automate! - - Learn about the available [automation triggers](/components/automation.html#triggers) - - Learn about the available [automation conditions](/components/automation.html#conditions) - - Learn about [scripts](/components/script.html) 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 the available [automation triggers](/components/automation/#triggers) + - Learn about the available [automation conditions](/components/automation/#conditions) + - Learn about [scripts](/components/script/) to help you trigger multiple actions and delays + - 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

    diff --git a/source/getting-started/autostart.markdown b/source/getting-started/autostart.markdown index 485171218c8..a0cdd6f6458 100644 --- a/source/getting-started/autostart.markdown +++ b/source/getting-started/autostart.markdown @@ -125,4 +125,4 @@ Home Assistant has been uninstalled. -###[« Back to Getting Started](/getting-started/index.html) +###[« Back to Getting Started](/getting-started/index/) diff --git a/source/getting-started/configuration.markdown b/source/getting-started/configuration.markdown index f2238791327..00f92e6dc5e 100644 --- a/source/getting-started/configuration.markdown +++ b/source/getting-started/configuration.markdown @@ -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. 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/).

    You will have to restart Home Assistant for changes in configuration.yaml to take effect. @@ -64,7 +64,7 @@ http: ### {% 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 %} @@ -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 like [DuckDNS](https://www.duckdns.org/). -###[Next step: Setting up devices »](/getting-started/devices.html) \ No newline at end of file +###[Next step: Setting up devices »](/getting-started/devices/) \ No newline at end of file diff --git a/source/getting-started/devices.markdown b/source/getting-started/devices.markdown index dc051adc19d..43f237c53df 100644 --- a/source/getting-started/devices.markdown +++ b/source/getting-started/devices.markdown @@ -11,7 +11,7 @@ footer: true 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 -[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 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 configuration.yam

    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 %} @@ -60,4 +60,4 @@ homeassistant: ``` -###[Next step: Setting up presence detection »](/getting-started/presence-detection.html) +###[Next step: Setting up presence detection »](/getting-started/presence-detection/) diff --git a/source/getting-started/index.markdown b/source/getting-started/index.markdown index f876131c861..5d2d12bb858 100644 --- a/source/getting-started/index.markdown +++ b/source/getting-started/index.markdown @@ -77,7 +77,7 @@ Running these commands will: ### {% 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: @@ -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. ### {% 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: ```bash @@ -98,4 +98,4 @@ To update Home Assistant to the latest release: pip3 install \-\-upgrade homeassistant ``` -###[Next step: Configuring Home Assistant »](/getting-started/configuration.html) +###[Next step: Configuring Home Assistant »](/getting-started/configuration/) diff --git a/source/getting-started/presence-detection.markdown b/source/getting-started/presence-detection.markdown index 949dc4afd7b..ad4e727f10c 100644 --- a/source/getting-started/presence-detection.markdown +++ b/source/getting-started/presence-detection.markdown @@ -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). 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 -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).

    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 [conditions][condition] for automation. -###[Next step: Setting up automation »](/getting-started/automation.html) +###[Next step: Setting up automation »](/getting-started/automation/) [routers]: /components/#presence -[nmap]: /components/device_tracker.nmap_scanner.html -[ha-owntracks]: /components/device_tracker.owntracks.html -[mqtt-self]: /components/mqtt.html#run-your-own -[mqtt-cloud]: /components/mqtt.html#cloudmqtt -[zone]: /components/zone.html -[trigger]: /components/automation.html#zone-trigger -[condition]: /components/automation.html#zone-condition +[nmap]: /components/device_tracker.nmap_scanner/ +[ha-owntracks]: /components/device_tracker.owntracks/ +[mqtt-self]: /components/mqtt/#run-your-own +[mqtt-cloud]: /components/mqtt/#cloudmqtt +[zone]: /components/zone/ +[trigger]: /components/automation/#zone-trigger +[condition]: /components/automation/#zone-condition diff --git a/source/getting-started/troubleshooting.markdown b/source/getting-started/troubleshooting.markdown index 4192c68802e..f11e64aa0a7 100644 --- a/source/getting-started/troubleshooting.markdown +++ b/source/getting-started/troubleshooting.markdown @@ -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 ``` -###[« Back to Getting Started](/getting-started/index.html) +###[« Back to Getting Started](/getting-started/index/)