diff --git a/source/_docs/configuration/remote.markdown b/source/_docs/configuration/remote.markdown index bd0d0ba60b5..77bacfd35fd 100644 --- a/source/_docs/configuration/remote.markdown +++ b/source/_docs/configuration/remote.markdown @@ -7,7 +7,6 @@ sidebar: true comments: false sharing: true footer: true -redirect_from: /getting-started/basic/#remote-access --- If you're interested in logging in to Home Assistant while away, you'll have to make your instance remotely accessible. Remember to follow the [securing checklist](/docs/configuration/securing/) before doing this. diff --git a/source/_docs/mqtt/broker.markdown b/source/_docs/mqtt/broker.markdown index 4421d209be5..47ea1bb73e6 100644 --- a/source/_docs/mqtt/broker.markdown +++ b/source/_docs/mqtt/broker.markdown @@ -8,7 +8,6 @@ comments: false sharing: true footer: true logo: mqtt.png -redirect_from: /components/mqtt/#picking-a-broker --- The MQTT component needs you to run an MQTT broker for Home Assistant to connect to. There are four options, each with various degrees of ease of setup and privacy. diff --git a/source/_docs/mqtt/discovery.markdown b/source/_docs/mqtt/discovery.markdown index 51eae400c43..3242a5f86d2 100644 --- a/source/_docs/mqtt/discovery.markdown +++ b/source/_docs/mqtt/discovery.markdown @@ -8,7 +8,6 @@ comments: false sharing: true footer: true logo: mqtt.png -redirect_from: /components/mqtt/#discovery --- The discovery of MQTT devices will enable one to use MQTT devices with only minimal configuration effort on the side of Home Assistant. The configuration is done on the device itself and the topic used by the device. Similar to the [HTTP binary sensor](/components/binary_sensor.http/) and the [HTTP sensor](/components/sensor.http/). The basic idea is that the device itself adds its configuration into your `configuration.yaml` automatically. To prevent multiple identical entries if a device reconnects a unique identifier is necessary. Two parts are required on the device side: The configuration topic which contains the necessary device type and unique identifier and the remaining device configuration without the device type. diff --git a/source/_docs/mqtt/logging.markdown b/source/_docs/mqtt/logging.markdown index 08b84f52777..999e24988f0 100644 --- a/source/_docs/mqtt/logging.markdown +++ b/source/_docs/mqtt/logging.markdown @@ -8,7 +8,6 @@ comments: false sharing: true footer: true logo: mqtt.png -redirect_from: /components/mqtt/#logging --- The [logger](/components/logger/) component allow the logging of received MQTT messages. diff --git a/source/_docs/mqtt/processing_json.markdown b/source/_docs/mqtt/processing_json.markdown index b10558655cb..552dd081676 100644 --- a/source/_docs/mqtt/processing_json.markdown +++ b/source/_docs/mqtt/processing_json.markdown @@ -8,7 +8,6 @@ comments: false sharing: true footer: true logo: mqtt.png -redirect_from: /components/mqtt/#processing-json --- The MQTT [switch](/components/switch.mqtt/) and [sensor](/components/sensor.mqtt/) platforms support processing JSON over MQTT messages and parsing them using JSONPath. JSONPath allows you to specify where in the JSON the value resides that you want to use. The following examples will always return the value `100`. diff --git a/source/_docs/mqtt/service.markdown b/source/_docs/mqtt/service.markdown index 0b3e778fdf2..d751856fe4c 100644 --- a/source/_docs/mqtt/service.markdown +++ b/source/_docs/mqtt/service.markdown @@ -8,7 +8,6 @@ comments: false sharing: true footer: true logo: mqtt.png -redirect_from: /components/mqtt/#publish-service --- The MQTT component will register the service `publish` which allows publishing messages to MQTT topics. There are two ways of specifying your payload. You can either use `payload` to hard-code a payload or use `payload_template` to specify a [template](/topics/templating/) that will be rendered to generate the payload. diff --git a/source/_docs/mqtt/testing.markdown b/source/_docs/mqtt/testing.markdown index 3cc565d0511..f71ac52e2f1 100644 --- a/source/_docs/mqtt/testing.markdown +++ b/source/_docs/mqtt/testing.markdown @@ -8,7 +8,6 @@ comments: false sharing: true footer: true logo: mqtt.png -redirect_from: /components/mqtt/#testing-your-setup --- The `mosquitto` broker package ships commandline tools (often as `*-clients` package) to send and receive MQTT messages. As an alternative have a look at [hbmqtt_pub](http://hbmqtt.readthedocs.org/en/latest/references/hbmqtt_pub.html) and [hbmqtt_sub](http://hbmqtt.readthedocs.org/en/latest/references/hbmqtt_sub.html) which are provided by HBMQTT. For sending test messages to a broker running on localhost check the example below: diff --git a/source/_docs/tools/benchmark.markdown b/source/_docs/tools/benchmark.markdown index c95894489e3..04ac884068c 100644 --- a/source/_docs/tools/benchmark.markdown +++ b/source/_docs/tools/benchmark.markdown @@ -7,7 +7,6 @@ sidebar: true comments: false sharing: true footer: true -redirect_from: /docs/tools/scripts/#benchmark --- For testing the performance of Home Assistant the Benchmark script runs until you exit using Control+C. diff --git a/source/_docs/tools/check_config.markdown b/source/_docs/tools/check_config.markdown index f3a926783e2..f9a31e0374d 100644 --- a/source/_docs/tools/check_config.markdown +++ b/source/_docs/tools/check_config.markdown @@ -7,7 +7,6 @@ sidebar: true comments: false sharing: true footer: true -redirect_from: /docs/tools/scripts/#configuration-check --- Test any changes to your `configuration.yaml` file before launching Home Assistant. This script allows you to test changes without the need to restart Home Assistant. diff --git a/source/_docs/tools/credstash.markdown b/source/_docs/tools/credstash.markdown index 0d419a104f4..023ee239988 100644 --- a/source/_docs/tools/credstash.markdown +++ b/source/_docs/tools/credstash.markdown @@ -7,7 +7,6 @@ sidebar: true comments: false sharing: true footer: true -redirect_from: /docs/configuration/secrets/#storing-passwords-securely-in-aws --- Using [Credstash](https://github.com/fugue/credstash) is an alternative way to `secrets.yaml`. They can be managed from the command line via the credstash script. diff --git a/source/_docs/tools/db_migrator.markdown b/source/_docs/tools/db_migrator.markdown index bdce8d1ab04..68127935ae3 100644 --- a/source/_docs/tools/db_migrator.markdown +++ b/source/_docs/tools/db_migrator.markdown @@ -7,7 +7,6 @@ sidebar: true comments: false sharing: true footer: true -redirect_from: /components/influxdb/#data-migration ---

diff --git a/source/_docs/tools/ensure_config.markdown b/source/_docs/tools/ensure_config.markdown index c9539398567..596c44d5717 100644 --- a/source/_docs/tools/ensure_config.markdown +++ b/source/_docs/tools/ensure_config.markdown @@ -7,7 +7,6 @@ sidebar: true comments: false sharing: true footer: true -redirect_from: /docs/tools/scripts/#existence-of-configuration --- This script checks if the `configuration.yaml` file exists. If the file is not available, one is created. diff --git a/source/_docs/tools/influxdb_import.markdown b/source/_docs/tools/influxdb_import.markdown index b8bea1046cc..8ff3d85e7b8 100644 --- a/source/_docs/tools/influxdb_import.markdown +++ b/source/_docs/tools/influxdb_import.markdown @@ -7,7 +7,6 @@ sidebar: true comments: false sharing: true footer: true -redirect_from: /components/influxdb/#data-import-script --- If you want to import all the recorded data from your recorder database you can use the data import script. It will read all your state_change events from the database and add them as data-points to the InfluxDB. You can specify the source database either by pointing the `--config` option to the config directory which includes the default SQLite database or by giving a sqlalchemy connection URI with `--uri`. diff --git a/source/_docs/tools/keyring.markdown b/source/_docs/tools/keyring.markdown index 6434337b39f..be4f2634a0d 100644 --- a/source/_docs/tools/keyring.markdown +++ b/source/_docs/tools/keyring.markdown @@ -7,7 +7,6 @@ sidebar: true comments: false sharing: true footer: true -redirect_from: /docs/configuration/secrets/#storing-passwords-in-a-keyring-managed-by-your-os --- Using [Keyring](https://github.com/jaraco/keyring) is an alternative way to `secrets.yaml`. The secrets can be managed from the command line via the `keyring` script.