From 69a0bfd29ac37eaf8026cc33f966268f41f10ee1 Mon Sep 17 00:00:00 2001 From: Franck Nijhof Date: Sat, 19 Jan 2019 11:56:44 +0100 Subject: [PATCH] :hammer: Replaces all hardlinks with relative ones (#8207) --- source/_addons/mosquitto.markdown | 4 ++-- source/_components/alarmdecoder.markdown | 2 +- source/_components/binary_sensor.flic.markdown | 2 +- source/_components/binary_sensor.point.markdown | 2 +- source/_components/binary_sensor.rainmachine.markdown | 2 +- source/_components/binary_sensor.workday.markdown | 2 +- source/_components/bmw_connected_drive.markdown | 2 +- source/_components/camera.ffmpeg.markdown | 2 +- source/_components/device_tracker.googlehome.markdown | 2 +- source/_components/dialogflow.markdown | 2 +- source/_components/homematic.markdown | 2 +- source/_components/ifttt.markdown | 2 +- source/_components/image_processing.facebox.markdown | 4 ++-- source/_components/image_processing.tensorflow.markdown | 2 +- source/_components/insteon.markdown | 2 +- source/_components/konnected.markdown | 2 +- source/_components/light.nanoleaf_aurora.markdown | 2 +- source/_components/mailgun.markdown | 2 +- source/_components/media_player.plex.markdown | 2 +- source/_components/point.markdown | 2 +- source/_components/qwikswitch.markdown | 2 +- source/_components/sensor.mitemp_bt.markdown | 2 +- source/_components/sensor.rainmachine.markdown | 2 +- source/_components/sensor.ruter.markdown | 2 +- source/_components/switch.rainmachine.markdown | 2 +- source/_components/twilio.markdown | 2 +- source/_docs/authentication/multi-factor-auth.markdown | 2 +- source/_docs/configuration.markdown | 2 +- source/_docs/configuration/securing.markdown | 2 +- source/_docs/configuration/troubleshooting.markdown | 2 +- source/_docs/z-wave.markdown | 2 +- source/_docs/z-wave/installation.markdown | 2 +- source/_lovelace/shopping-list.markdown | 2 +- source/_lovelace/weather-forecast.markdown | 2 +- source/_posts/2018-04-22-hassio-2018.markdown | 2 +- source/_posts/2018-07-06-release-73.markdown | 2 +- source/_posts/2018-07-11-hassio-images.markdown | 2 +- source/help/reporting_issues.markdown | 4 ++-- 38 files changed, 41 insertions(+), 41 deletions(-) diff --git a/source/_addons/mosquitto.markdown b/source/_addons/mosquitto.markdown index 26d93276cc3..86d5c2316a3 100644 --- a/source/_addons/mosquitto.markdown +++ b/source/_addons/mosquitto.markdown @@ -57,7 +57,7 @@ To use the Mosquitto as [broker](/docs/mqtt/broker/#run-your-own), go to the int #### {% linkable_title Using Mosquitto with Hass.io %} -1. Install the [Mosquitto add-on](https://www.home-assistant.io/addons/mosquitto/) with the default configuration via 'Hass.io > ADD-ON STORE'. (Don't forget to start the add-on & verify that 'Start on boot' is enabled.) +1. Install the [Mosquitto add-on](/addons/mosquitto/) with the default configuration via 'Hass.io > ADD-ON STORE'. (Don't forget to start the add-on & verify that 'Start on boot' is enabled.) 2. Create a new user for MQTT via the `Configuration > Users (manage users)`. (Note: This name cannot be "homeassistant" or "addon") @@ -71,7 +71,7 @@ To use the Mosquitto as [broker](/docs/mqtt/broker/#run-your-own), go to the int ``` Note: .yaml modifications are not required. -See [testing your setup](https://www.home-assistant.io/docs/mqtt/testing/) to verify the steps above. +See [testing your setup](/docs/mqtt/testing/) to verify the steps above. ### {% linkable_title Disable listening on insecure (1883) ports %} diff --git a/source/_components/alarmdecoder.markdown b/source/_components/alarmdecoder.markdown index 01d9bfb8053..0c47d81bb72 100644 --- a/source/_components/alarmdecoder.markdown +++ b/source/_components/alarmdecoder.markdown @@ -91,7 +91,7 @@ zones: required: true type: string type: - description: "A type for the zone. Here you can find a list of [Device Classes](https://www.home-assistant.io/components/binary_sensor/#device-class)." + description: "A type for the zone. Here you can find a list of [Device Classes](/components/binary_sensor/#device-class)." required: false default: opening type: string diff --git a/source/_components/binary_sensor.flic.markdown b/source/_components/binary_sensor.flic.markdown index dd70d2eb4cd..ef22b9b5e8e 100644 --- a/source/_components/binary_sensor.flic.markdown +++ b/source/_components/binary_sensor.flic.markdown @@ -19,7 +19,7 @@ The platform does not directly interact with the buttons, *but communicates with #### {% linkable_title Service setup %} -If you are using Hass.io, you can run the service locally by [installing](https://www.home-assistant.io/hassio/installing_third_party_addons/) the flicd add-on from [pschmitt's repository](https://github.com/pschmitt/hassio-addons). On a Hass.io installation that's not yet based on HassOS, you also need to install the [bluetooth add-on](/addons/bluetooth_bcm43xx/). +If you are using Hass.io, you can run the service locally by [installing](/hassio/installing_third_party_addons/) the flicd add-on from [pschmitt's repository](https://github.com/pschmitt/hassio-addons). On a Hass.io installation that's not yet based on HassOS, you also need to install the [bluetooth add-on](/addons/bluetooth_bcm43xx/). For instructions on how to install the service manually, visit the GitHub repository of the service for [Linux](https://github.com/50ButtonsEach/fliclib-linux-hci), [OS X](https://github.com/50ButtonsEach/flic-service-osx) or [Windows](https://github.com/50ButtonsEach/fliclib-windows). diff --git a/source/_components/binary_sensor.point.markdown b/source/_components/binary_sensor.point.markdown index dadf24d5aa8..f12d9275172 100644 --- a/source/_components/binary_sensor.point.markdown +++ b/source/_components/binary_sensor.point.markdown @@ -31,5 +31,5 @@ Each Point exposes the following binary sensors: For installation instructions, see [the Point component](/components/point/).

-The events sent from the Point is also sent as a webhook back to Home Assistant with `event_type` as `point_webhook_received`, please consider the documentation for the [IFTT](https://www.home-assistant.io/components/ifttt/) component on how to write automations for webhooks. +The events sent from the Point is also sent as a webhook back to Home Assistant with `event_type` as `point_webhook_received`, please consider the documentation for the [IFTT](/components/ifttt/) component on how to write automations for webhooks.

diff --git a/source/_components/binary_sensor.rainmachine.markdown b/source/_components/binary_sensor.rainmachine.markdown index 0a3072ad0b6..1cf2b676306 100644 --- a/source/_components/binary_sensor.rainmachine.markdown +++ b/source/_components/binary_sensor.rainmachine.markdown @@ -17,7 +17,7 @@ The `rainmachine` binary sensor platform allows you to view crucial sensor data within a [RainMachine smart Wi-Fi sprinkler controller](http://www.rainmachine.com/).

-You must have the [RainMachine component](https://www.home-assistant.io/components/rainmachine/) +You must have the [RainMachine component](/components/rainmachine/) configured to use this platform. After configuring that component, binary sensors automatically appear.

diff --git a/source/_components/binary_sensor.workday.markdown b/source/_components/binary_sensor.workday.markdown index f9526ed891a..75cd8c6e271 100644 --- a/source/_components/binary_sensor.workday.markdown +++ b/source/_components/binary_sensor.workday.markdown @@ -96,6 +96,6 @@ automation: ```

-Please remember that [as explained here](https://www.home-assistant.io/docs/configuration/devices/) you can only have a single `automation:` entry. Add the automation to your existing automations. +Please remember that [as explained here](/docs/configuration/devices/) you can only have a single `automation:` entry. Add the automation to your existing automations.

diff --git a/source/_components/bmw_connected_drive.markdown b/source/_components/bmw_connected_drive.markdown index e448407a08f..67002468a92 100644 --- a/source/_components/bmw_connected_drive.markdown +++ b/source/_components/bmw_connected_drive.markdown @@ -22,7 +22,7 @@ This component provides the following platforms: - Device tracker: The location of your car. - Lock: Control the lock of your car. - Sensors: Mileage, remaining range, remaining fuel, charging time remaining (electric cars), charging status (electric cars), remaining range electric (electric cars). - - Services: Turn on air condition, sound the horn, flash the lights and update the state. More details can be found [here](https://www.home-assistant.io/components/bmw_connected_drive/#services). + - Services: Turn on air condition, sound the horn, flash the lights and update the state. More details can be found [here](/components/bmw_connected_drive/#services). ## {% linkable_title Configuration %} diff --git a/source/_components/camera.ffmpeg.markdown b/source/_components/camera.ffmpeg.markdown index 7bf659ce119..09f2cffc814 100644 --- a/source/_components/camera.ffmpeg.markdown +++ b/source/_components/camera.ffmpeg.markdown @@ -17,7 +17,7 @@ The `ffmpeg` platform allows you to use any video feed as a camera in Home Assis ## {% linkable_title Configuration %} -To enable your FFmpeg feed in your installation you must first configure the [ffmpeg component](https://www.home-assistant.io/components/ffmpeg/), then add the following to your `configuration.yaml` file: +To enable your FFmpeg feed in your installation you must first configure the [ffmpeg component](/components/ffmpeg/), then add the following to your `configuration.yaml` file: ```yaml # Example configuration.yaml entry diff --git a/source/_components/device_tracker.googlehome.markdown b/source/_components/device_tracker.googlehome.markdown index 34a821bbd36..6389280a22c 100644 --- a/source/_components/device_tracker.googlehome.markdown +++ b/source/_components/device_tracker.googlehome.markdown @@ -45,4 +45,4 @@ Devices will appear in the format `devicetracker._ The Point is just active occasionally so the sensors are only updated every hour or so. -The events sent from the Point is sent as a webhook back to Home Assistant with `event_type` as `point_webhook_received`, please consider the documentation for the [IFTT](https://www.home-assistant.io/components/ifttt/) component on how to write automations for webhooks. +The events sent from the Point is sent as a webhook back to Home Assistant with `event_type` as `point_webhook_received`, please consider the documentation for the [IFTT](/components/ifttt/) component on how to write automations for webhooks.

diff --git a/source/_components/qwikswitch.markdown b/source/_components/qwikswitch.markdown index b176681d03e..9017de6e717 100644 --- a/source/_components/qwikswitch.markdown +++ b/source/_components/qwikswitch.markdown @@ -75,7 +75,7 @@ sensors: default: false type: string class: - description: The [class](https://www.home-assistant.io/components/binary_sensor) or binary_sensor. Only applicable to binary_sensors. + description: The [class](components/binary_sensor) or binary_sensor. Only applicable to binary_sensors. required: false default: door type: string diff --git a/source/_components/sensor.mitemp_bt.markdown b/source/_components/sensor.mitemp_bt.markdown index d7bdbccaffe..5cf0f59fb12 100644 --- a/source/_components/sensor.mitemp_bt.markdown +++ b/source/_components/sensor.mitemp_bt.markdown @@ -20,7 +20,7 @@ The `mitemp_bt` sensor platform allows one to monitor room temperature and humid Depending on the operating system you're running, you have to configure the proper Bluetooth backend on your system: - On [Hass.io](/hassio/installation/): `mitemp_bt` will work out of the box as long as the host supports Bluetooth (like the Raspberry Pi does). -- On a [generic Docker installation](https://www.home-assistant.io/docs/installation/docker/): Works out of the box with `--net=host` and properly configured Bluetooth on the host. +- On a [generic Docker installation](/docs/installation/docker/): Works out of the box with `--net=host` and properly configured Bluetooth on the host. - On other Linux systems: - Preferred solution: Install the `bluepy` and `btlewrap` library (via pip). When using a virtual environment, make sure to use install the library in the right one. - Fallback solution: Install `btlewrap` library (via pip) and `gatttool` via your package manager. Depending on the distribution, the package name might be: `bluez`, `bluetooth` or `bluez-deprecated`. diff --git a/source/_components/sensor.rainmachine.markdown b/source/_components/sensor.rainmachine.markdown index 4db41b38eaf..76228738190 100644 --- a/source/_components/sensor.rainmachine.markdown +++ b/source/_components/sensor.rainmachine.markdown @@ -17,7 +17,7 @@ The `rainmachine` sensor platform allows you to view crucial sensor data within a [RainMachine smart Wi-Fi sprinkler controller](http://www.rainmachine.com/).

-You must have the [RainMachine component](https://www.home-assistant.io/components/rainmachine/) +You must have the [RainMachine component](/components/rainmachine/) configured to use this platform. After configuring that component, sensors automatically appear.

diff --git a/source/_components/sensor.ruter.markdown b/source/_components/sensor.ruter.markdown index 1735623e084..a67bb96fa02 100644 --- a/source/_components/sensor.ruter.markdown +++ b/source/_components/sensor.ruter.markdown @@ -14,7 +14,7 @@ ha_release: 0.83 ---

-The API used for this sensor is shutting down soon, you should consider starting to use the [`entur_public_transport`](https://www.home-assistant.io/components/sensor.entur_public_transport/) sensor before that happen. +The API used for this sensor is shutting down soon, you should consider starting to use the [`entur_public_transport`](/components/sensor.entur_public_transport/) sensor before that happen. To read the deprecation warning visit [ruter.no/labs](https://ruter.no/labs/),

diff --git a/source/_components/switch.rainmachine.markdown b/source/_components/switch.rainmachine.markdown index 982220ccacb..2f39f862d8e 100644 --- a/source/_components/switch.rainmachine.markdown +++ b/source/_components/switch.rainmachine.markdown @@ -17,7 +17,7 @@ The `rainmachine` switch platform allows you to control programs and zones within a [RainMachine smart Wi-Fi sprinkler controller](http://www.rainmachine.com/).

-You must have the [RainMachine component](https://www.home-assistant.io/components/rainmachine/) +You must have the [RainMachine component](/components/rainmachine/) configured to use this platform. After configuring that component, switches will automatically appear.

diff --git a/source/_components/twilio.markdown b/source/_components/twilio.markdown index 4908cde575c..f4f60e7cf7e 100644 --- a/source/_components/twilio.markdown +++ b/source/_components/twilio.markdown @@ -43,7 +43,7 @@ auth_token: After configuring the base Twilio component, add and configure either or both of the [twilio SMS](/components/notify.twilio_sms/) and [twilio Phone](/components/notify.twilio_call) components to utilize the notification functionality. -To be able to receive events from Twilio, your Home Assistant instance needs to be accessible from the web ([Hass.io instructions](/addons/duckdns/)) and you need to have the `base_url` configured for the HTTP component ([docs](https://www.home-assistant.io/components/http/#base_url)). +To be able to receive events from Twilio, your Home Assistant instance needs to be accessible from the web ([Hass.io instructions](/addons/duckdns/)) and you need to have the `base_url` configured for the HTTP component ([docs](/components/http/#base_url)). To set it up, go to the integrations page in the configuration screen and find Twilio. Click on configure. Follow the instructions on the screen to configure Twilio. diff --git a/source/_docs/authentication/multi-factor-auth.markdown b/source/_docs/authentication/multi-factor-auth.markdown index be55b3118ce..16ecd5b8e87 100644 --- a/source/_docs/authentication/multi-factor-auth.markdown +++ b/source/_docs/authentication/multi-factor-auth.markdown @@ -65,7 +65,7 @@ TOTP is _time based_ so it relies on your Home Assistant clock being accurate. I ### {% linkable_title Notify multi-factor authentication module %} -The Notify MFA module uses the [notify component](https://www.home-assistant.io/components/notify/) to send you an [HMAC-based One-Time Password](https://en.wikipedia.org/wiki/HMAC-based_One-time_Password_algorithm). It is typically sent to your phone, but can be sent to any destination supported by a `notify` service. You use this password to log in. +The Notify MFA module uses the [notify component](/components/notify/) to send you an [HMAC-based One-Time Password](https://en.wikipedia.org/wiki/HMAC-based_One-time_Password_algorithm). It is typically sent to your phone, but can be sent to any destination supported by a `notify` service. You use this password to log in. #### {% linkable_title Setting up TOTP %} diff --git a/source/_docs/configuration.markdown b/source/_docs/configuration.markdown index f97eb07c867..5d70b357c0d 100644 --- a/source/_docs/configuration.markdown +++ b/source/_docs/configuration.markdown @@ -38,7 +38,7 @@ If you run into trouble while configuring Home Assistant, have a look at the [co You will have to restart Home Assistant for most changes to `configuration.yaml` to take effect. You can load changes to [automations](/docs/automation/), [customize](/docs/configuration/customizing-devices/), [groups](/components/group/), and [scripts](/components/script/) without restarting if you're not using [packages](/docs/configuration/packages/).

-If you've made any changes, remember to [check your configuration](https://www.home-assistant.io/docs/configuration/troubleshooting/#problems-with-the-configuration) before trying to reload or restart. +If you've made any changes, remember to [check your configuration](/docs/configuration/troubleshooting/#problems-with-the-configuration) before trying to reload or restart.

## {% linkable_title Migrating to a new system %} diff --git a/source/_docs/configuration/securing.markdown b/source/_docs/configuration/securing.markdown index 85117013ff5..945f1c3e834 100644 --- a/source/_docs/configuration/securing.markdown +++ b/source/_docs/configuration/securing.markdown @@ -55,4 +55,4 @@ For remote access for a component, for example, a device tracker, you have to en * A [self-signed certificate](/cookbook/tls_self_signed_certificate/) - be warned though, some services will refuse to work with self-signed certificates 3. Optionally use a proxy like [NGINX](/docs/ecosystem/nginx/), [Apache](/cookbook/apache_configuration/), or another. These allow you to provide finer-grained access. You could use this to limit access to specific parts of the API (for example, only `/api/owntracks/`) 4. Enable IP Filtering and configure a low [Login Attempts Threshold](/components/http/) -5. If you use a proxy then install [fail2ban](https://www.fail2ban.org/wiki/index.php/Main_Page) to [monitor your proxy logs](https://www.home-assistant.io/cookbook/fail2ban/) (or Home Assistant logs) for failed authentication +5. If you use a proxy then install [fail2ban](https://www.fail2ban.org/wiki/index.php/Main_Page) to [monitor your proxy logs](/cookbook/fail2ban/) (or Home Assistant logs) for failed authentication diff --git a/source/_docs/configuration/troubleshooting.markdown b/source/_docs/configuration/troubleshooting.markdown index f76ca7086a0..03efee288be 100644 --- a/source/_docs/configuration/troubleshooting.markdown +++ b/source/_docs/configuration/troubleshooting.markdown @@ -26,7 +26,7 @@ If you have incorrect entries in your configuration files you can use the [`chec One of the most common problems with Home Assistant is an invalid `configuration.yaml` file. - - You can test your configuration using the command line with: `hass --script check_config`. On Hass.io you can use the [hassio command](https://www.home-assistant.io/hassio/commandline/#home-assistant): `hassio homeassistant check`. + - You can test your configuration using the command line with: `hass --script check_config`. On Hass.io you can use the [hassio command](/hassio/commandline/#home-assistant): `hassio homeassistant check`. - You can verify your configuration's yaml structure using [this online YAML parser](http://yaml-online-parser.appspot.com/) or [YAML Lint](http://www.yamllint.com/). - To learn more about the quirks of YAML, read [YAML IDIOSYNCRASIES](https://docs.saltstack.com/en/latest/topics/troubleshooting/yaml_idiosyncrasies.html) by SaltStack (the examples there are specific to SaltStack, but do explain YAML issues well). diff --git a/source/_docs/z-wave.markdown b/source/_docs/z-wave.markdown index 6df8aca7acf..caf4e3ad221 100644 --- a/source/_docs/z-wave.markdown +++ b/source/_docs/z-wave.markdown @@ -42,4 +42,4 @@ You can get more information on the [available services](/docs/z-wave/services/) When you toggle a switch or control a light locally you may find that it takes some time for that to be reflected in Home Assistant. That's because Lutron had patents on the status updates using the *Hail* command class, the traditional way of allowing devices to tell the controller that something happened locally. The same result can be achieved through the *Association* command class, or *Central Scene* command class (though, *Central Scene* isn't [fully supported](https://github.com/OpenZWave/open-zwave/pull/1125) in OpenZWave). -If you search [the Z-Wave products database](http://products.z-wavealliance.org/) for your product and it lists one of those in the **Controlled** command classes (not the **Supported** command classes), then your device will be able to report state changes when they happen. If it doesn't then updates may either happen eventually, or you may need to (carefully) [enable polling](https://www.home-assistant.io/docs/z-wave/control-panel/#entities-of-this-node). +If you search [the Z-Wave products database](http://products.z-wavealliance.org/) for your product and it lists one of those in the **Controlled** command classes (not the **Supported** command classes), then your device will be able to report state changes when they happen. If it doesn't then updates may either happen eventually, or you may need to (carefully) [enable polling](/docs/z-wave/control-panel/#entities-of-this-node). diff --git a/source/_docs/z-wave/installation.markdown b/source/_docs/z-wave/installation.markdown index e9c0ae6068b..f1db0bf8d32 100644 --- a/source/_docs/z-wave/installation.markdown +++ b/source/_docs/z-wave/installation.markdown @@ -63,7 +63,7 @@ network_key: type: string default: None config_path: - description: "The path to the Python OpenZWave configuration files. NOTE: there is also the [update_config service](https://www.home-assistant.io/docs/z-wave/services/) to perform updating the config within python-openzwave automatically." + description: "The path to the Python OpenZWave configuration files. NOTE: there is also the [update_config service](/docs/z-wave/services/) to perform updating the config within python-openzwave automatically." required: false type: string default: the 'config' that is installed by python-openzwave diff --git a/source/_lovelace/shopping-list.markdown b/source/_lovelace/shopping-list.markdown index ec57df242c6..ab0d78462f4 100644 --- a/source/_lovelace/shopping-list.markdown +++ b/source/_lovelace/shopping-list.markdown @@ -12,7 +12,7 @@ footer: true The Shopping List Card allows you to add, edit, check-off, and clear items from your shopping list. -Setup of the [Shopping List Intent](https://www.home-assistant.io/components/shopping_list/) is required +Setup of the [Shopping List Intent](/components/shopping_list/) is required

Screenshot of the shopping list card diff --git a/source/_lovelace/weather-forecast.markdown b/source/_lovelace/weather-forecast.markdown index 2f9deb4f063..02095b64a19 100644 --- a/source/_lovelace/weather-forecast.markdown +++ b/source/_lovelace/weather-forecast.markdown @@ -43,5 +43,5 @@ name:

This card works only with platforms that define a `weather` entity. - E.g., it works with [Dark Sky](https://www.home-assistant.io/components/weather.darksky/) but not [Dark Sky Sensor](https://www.home-assistant.io/components/sensor.darksky/) + E.g., it works with [Dark Sky](/components/weather.darksky/) but not [Dark Sky Sensor](/components/sensor.darksky/)

diff --git a/source/_posts/2018-04-22-hassio-2018.markdown b/source/_posts/2018-04-22-hassio-2018.markdown index 90506053552..61e762341e0 100644 --- a/source/_posts/2018-04-22-hassio-2018.markdown +++ b/source/_posts/2018-04-22-hassio-2018.markdown @@ -58,7 +58,7 @@ Once our new installation images with HassioOS are released, you have to reflash - Restore your snapshot. - Enjoy a new and improved Hass.io -[last July]: https://www.home-assistant.io/blog/2017/07/25/introducing-hassio/ +[last July]: /blog/2017/07/25/introducing-hassio/ [the conclusion]: #what-hassio-users-should-do-to-prepare-for-these-updates [Buildroot]: https://buildroot.org/ [RAUC]: https://www.rauc.io/ diff --git a/source/_posts/2018-07-06-release-73.markdown b/source/_posts/2018-07-06-release-73.markdown index e63aea2452b..7468e27a5d7 100644 --- a/source/_posts/2018-07-06-release-73.markdown +++ b/source/_posts/2018-07-06-release-73.markdown @@ -11,7 +11,7 @@ categories: Release-Notes og_image: /images/blog/2018-07-0.73/lovelace-elements.png --- -Today we're releasing Home Assistant 0.73. First, let's talk security. Home Assistant has a lot of power. It can control all devices in your house and know what you're up to. That's why securing it is very important. It's absolutely wrong to connect your instance unsecured to the internet and hope no one will find it. All ports on all computers are regularly scanned by bad actors. Please read [our guidelines thoroughly](https://www.home-assistant.io/docs/configuration/securing/) and follow them. +Today we're releasing Home Assistant 0.73. First, let's talk security. Home Assistant has a lot of power. It can control all devices in your house and know what you're up to. That's why securing it is very important. It's absolutely wrong to connect your instance unsecured to the internet and hope no one will find it. All ports on all computers are regularly scanned by bad actors. Please read [our guidelines thoroughly](/docs/configuration/securing/) and follow them. In the meanwhile, we're also working hard on the new authentication system. A preview version is included in this release, more info on [our developer blog](https://developers.home-assistant.io/blog/2018/07/02/trying-new-auth.html). diff --git a/source/_posts/2018-07-11-hassio-images.markdown b/source/_posts/2018-07-11-hassio-images.markdown index bedab4d9f12..b9097a76be8 100644 --- a/source/_posts/2018-07-11-hassio-images.markdown +++ b/source/_posts/2018-07-11-hassio-images.markdown @@ -60,5 +60,5 @@ Feel free to jump into the project and help us to improve the documentation or o [Buildroot]: https://buildroot.org/ [AppArmor]: https://gitlab.com/apparmor/apparmor/wikis/home/ [USB stick]: https://github.com/home-assistant/hassos/blob/rel-1/Documentation/configuration.md#automatic -[installation]: https://www.home-assistant.io/hassio/installation/ +[installation]: /hassio/installation/ [Etcher]: https://etcher.io/ diff --git a/source/help/reporting_issues.markdown b/source/help/reporting_issues.markdown index 2bc89b048ca..5193c739e3c 100644 --- a/source/help/reporting_issues.markdown +++ b/source/help/reporting_issues.markdown @@ -37,8 +37,8 @@ There are many different ways to run Home Assistant. In this section please ment Please add the link to the documention of the component/platform in question. E.g., -- issue with the `random` sensor: [https://www.home-assistant.io/components/sensor.random/](/components/sensor.random/) -- issue with the `hue` component: [https://www.home-assistant.io/components/hue/](/components/hue/) +- issue with the `random` sensor: [/components/sensor.random/](/components/sensor.random/) +- issue with the `hue` component: [/components/hue/](/components/hue/) ### {% linkable_title Description of problem %}