-Be aware that `emulated_hue` doesn't work for new users of **Google Home** with `emulated_hue`. If you've not previously set this up and had it working, use the [Google Assistant component](/components/google_assistant/) or [Nabu Casa cloud](https://www.home-assistant.io/components/cloud) component.
+Be aware that `emulated_hue` doesn't work for new users of **Google Home** with `emulated_hue`. If you've not previously set this up and had it working, use the [Google Assistant component](/components/google_assistant/) or [Nabu Casa cloud](/components/cloud) component.
The `emulated_hue` integration provides a virtual Philips Hue bridge, written entirely in software, which allows services that work with the Hue API to interact with Home Assistant
diff --git a/source/_components/http.markdown b/source/_components/http.markdown
index 904de87d5db..5a204422e31 100644
--- a/source/_components/http.markdown
+++ b/source/_components/http.markdown
@@ -103,7 +103,7 @@ ssl_profile:
{% endconfiguration %}
-Configuring trusted_networks via the `http` integration will be deprecated and moved to `auth_providers` instead. For instructions, see trusted networks. In Home Assistant 0.89.0 and 0.89.1, you need place the trusted network under both `http` and `auth_providers` if you still want to use trusted networks features. You can remove it from `http` section starting from 0.89.2.
+Configuring trusted_networks via the `http` integration will be deprecated and moved to `auth_providers` instead. For instructions, see trusted networks. In Home Assistant 0.89.0 and 0.89.1, you need place the trusted network under both `http` and `auth_providers` if you still want to use trusted networks features. You can remove it from `http` section starting from 0.89.2.
The sample below shows a configuration entry with possible values:
diff --git a/source/_components/life360.markdown b/source/_components/life360.markdown
index a1cbf577849..91b7a157b10 100644
--- a/source/_components/life360.markdown
+++ b/source/_components/life360.markdown
@@ -131,7 +131,7 @@ However, in some circumstances, it might be helpful to limit which Life360 Circl
For a particular Member to be tracked, they must be included (or at least not excluded), and must be in at least one of the included Circles. See [example configuration](#circle-and-member-filtering-example) below.
-Note that Life360's app and website typically only show Members' first names. However, you must use their _full_ names here. If you're not sure what a Member's full name (i.e., first and last) is in Life360, ask them. Alternatively, you can set the [`logger`](https://www.home-assistant.io/components/logger/) to `debug` and look in `home-assistant.log`. The full names of all Life360 Circles & Members will be logged.
+Note that Life360's app and website typically only show Members' first names. However, you must use their _full_ names here. If you're not sure what a Member's full name (i.e., first and last) is in Life360, ask them. Alternatively, you can set the [`logger`](/components/logger/) to `debug` and look in `home-assistant.log`. The full names of all Life360 Circles & Members will be logged.
## Home - Home Assistant vs. Life360
@@ -139,7 +139,7 @@ Normally Home Assistant device trackers are "Home" when they enter `zone.home`.
## Home Assistant Zones & Life360 Places
-See [Zone documentation](https://www.home-assistant.io/components/zone/#home-zone) for details about how HA zones are defined. If you'd like to create HA zones from Life360 Places (e.g., to make HA's `zone.home` be identical to Life360's "Home Place"), make sure `logger` is set to `debug`. Then when HA starts the details of all the Places defined in the included Circles will be written to `home-assistant.log` in a format that can be copied into your configuration under `zone:`. E.g., you would see something like this:
+See [Zone documentation](/components/zone/#home-zone) for details about how HA zones are defined. If you'd like to create HA zones from Life360 Places (e.g., to make HA's `zone.home` be identical to Life360's "Home Place"), make sure `logger` is set to `debug`. Then when HA starts the details of all the Places defined in the included Circles will be written to `home-assistant.log` in a format that can be copied into your configuration under `zone:`. E.g., you would see something like this:
```text
2019-05-31 12:16:58 DEBUG (SyncWorker_3) [homeassistant.components.life360.device_tracker] My Family Circle: will be included, id=xxxxx
diff --git a/source/_components/netatmo.markdown b/source/_components/netatmo.markdown
index fdb8a0ffbb4..af5503ba578 100644
--- a/source/_components/netatmo.markdown
+++ b/source/_components/netatmo.markdown
@@ -99,9 +99,9 @@ That's it. You can copy and paste your new `client id` and `client secret` in yo
### Webhooks
-The Welcome and Presence cameras can send instant events to Home Assistant by using webhooks. There are different types of events, each with slightly different data attached. To enable the webhooks add `webhooks: true` to your configuration. It is also required to have your camera enabled in Home Assistant. You can do this either by manually setting up the [platform](https://www.home-assistant.io/components/camera.netatmo/) or by enabeling [discovery](https://www.home-assistant.io/components/netatmo/#discovery).
+The Welcome and Presence cameras can send instant events to Home Assistant by using webhooks. There are different types of events, each with slightly different data attached. To enable the webhooks add `webhooks: true` to your configuration. It is also required to have your camera enabled in Home Assistant. You can do this either by manually setting up the [platform](/components/camera.netatmo/) or by enabeling [discovery](/components/netatmo/#discovery).
-To be able to receive events from Netatmo, your Home Assistant instance needs to be accessible from the web ([Hass.io instructions](https://www.home-assistant.io/addons/duckdns/)) and you need to have the base_url configured for the HTTP integration ([docs](https://www.home-assistant.io/components/http/#base_url)).
+To be able to receive events from Netatmo, 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 integration ([docs](/components/http/#base_url)).
Events coming in from Netatmo will be available as events in Home Assistant and are fired as netatmo_*, along with their data. You can use this event to trigger automations.
@@ -141,7 +141,7 @@ The Welcome camera additionally has these attributes for `netatmo_person` events
| is_known | Boolean value if the person is known.
| face_url | URL to a picture of the person.
-The `netatmo_other` event passes all the webhook data through for all webhook events that don't match any of the above. Set the [level of logging](https://www.home-assistant.io/components/logger/) for the `netatmo` integration to `debug` to view the data in the Home Assistant logs.
+The `netatmo_other` event passes all the webhook data through for all webhook events that don't match any of the above. Set the [level of logging](/components/logger/) for the `netatmo` integration to `debug` to view the data in the Home Assistant logs.
### Services (only for webhooks)
@@ -149,7 +149,7 @@ There are two services to manually add and drop the webhooks. This might be usef
| Service | Description |
| ------- | ----------- |
-| addwebhook | Subscribe to webhooks. By default the automatically generated URL will be used. But you can pass `{"url": "https://yourdomain.com/yourwebhook/"}` as service data to the service call if you want to use a manually created [webhook trigger](https://www.home-assistant.io/docs/automation/trigger/#webhook-trigger). In this case you have to manually process the data that is sent by Netatmo.
+| addwebhook | Subscribe to webhooks. By default the automatically generated URL will be used. But you can pass `{"url": "https://yourdomain.com/yourwebhook/"}` as service data to the service call if you want to use a manually created [webhook trigger](/docs/automation/trigger/#webhook-trigger). In this case you have to manually process the data that is sent by Netatmo.
| dropwebhook | Unsubscribe existing webhooks.
## Binary Sensor
diff --git a/source/_components/osramlightify.markdown b/source/_components/osramlightify.markdown
index d67ee99b32f..956eb114621 100644
--- a/source/_components/osramlightify.markdown
+++ b/source/_components/osramlightify.markdown
@@ -66,7 +66,7 @@ The only thing that you can do out of the box is to track whether they are avail
Also for sensors a list of raw values is exposed as `sensor_values` attribute, and you can use them
in automations, if you know what particular values mean for your sensor.
-It is suggested to make [scan_interval](https://www.home-assistant.io/docs/configuration/platform_options/#scan-interval)
+It is suggested to make [scan_interval](/docs/configuration/platform_options/#scan-interval)
(30 seconds by default) less or equal to `interval_lightify_status`, oherwise the latter won't work
as expected. Shorter `scan_interval` may improve synchronization speed between individual lights and
groups. For example, if you turn on a group, all its lights may be updated to `on` immediately,
diff --git a/source/_components/person.markdown b/source/_components/person.markdown
index 0d240eb7351..f8c1dad8cd1 100644
--- a/source/_components/person.markdown
+++ b/source/_components/person.markdown
@@ -14,7 +14,7 @@ ha_qa_scale: internal
ha_release: 0.88
---
-The person integration allows connecting [device tracker](https://www.home-assistant.io/components/device_tracker/) entities to one or more person entities. The state updates of a connected device tracker will set the state of the person. When multiple device trackers are used, the state of person will be determined in this order:
+The person integration allows connecting [device tracker](/components/device_tracker/) entities to one or more person entities. The state updates of a connected device tracker will set the state of the person. When multiple device trackers are used, the state of person will be determined in this order:
1. If there are stationary trackers (non-GPS trackers, i.e., a router or Bluetooth 'device_trackers') presenting the status 'home', the tracker most recently updated will be used.
2. If there are trackers of type 'gps', then the most recently updated tracker will be used.
@@ -23,7 +23,7 @@ The person integration allows connecting [device tracker](https://www.home-assis
Let's say, for example, that you have 3 trackers: 'tracker_gps', 'tracker_router' and 'tracker_ble'.
1. You're at home, all 3 devices show status 'home' - status of your Person entity will be 'home' with source 'tracker_router' or 'tracker_ble', whichever was most recently updated.
-2. You just left home. 'tracker_gps' shows status 'not_home', but the other two trackers show status 'home' (they may not have yet updated due to their 'consider_home' setting see [device_tracker](https://www.home-assistant.io/components/device_tracker/#configuring-a-device_tracker-platform)). Since the stationary trackers have priority, you are considered 'home'.
+2. You just left home. 'tracker_gps' shows status 'not_home', but the other two trackers show status 'home' (they may not have yet updated due to their 'consider_home' setting see [device_tracker](/components/device_tracker/#configuring-a-device_tracker-platform)). Since the stationary trackers have priority, you are considered 'home'.
3. After some time, both stationary trackers show status 'not_home'. Now your Person entity has status 'not_home' with source 'tracker_gps'.
4. While you are away from home, your Home Assistant is restarted. Until 'tracker_gps' receives an update, your status will be determined by the stationary trackers, since they will have the most recent update after a restart. Obviously, the status will be 'not_home'.
5. Then you're going into a zone you have defined as 'zone1', 'tracker_gps' sends an update, and now your status is 'zone1' with source 'tracker_gps'.
@@ -32,7 +32,7 @@ Let's say, for example, that you have 3 trackers: 'tracker_gps', 'tracker_router
TL;DR: When you're at home, your position is determined first by stationary trackers (if any) and then by GPS. When you're outside your home, your position is determined firstly by GPS and then by stationary trackers.
-**Hint**: When you use multiple device trackers together, especially stationary and GPS trackers, it's advisable to set `consider_home` for stationary trackers as low as possible see [device_tracker](https://www.home-assistant.io/components/device_tracker/#configuring-a-device_tracker-platform)).
+**Hint**: When you use multiple device trackers together, especially stationary and GPS trackers, it's advisable to set `consider_home` for stationary trackers as low as possible see [device_tracker](/components/device_tracker/#configuring-a-device_tracker-platform)).
You can manage persons via the UI from the person page inside the configuration panel or via `YAML` in your `configuration.yaml` file.
diff --git a/source/_components/point.markdown b/source/_components/point.markdown
index 9882b0b518f..8c9915fb08b 100644
--- a/source/_components/point.markdown
+++ b/source/_components/point.markdown
@@ -60,7 +60,7 @@ The integration supports the following device types within Home Assistant:
- [Sensor](#sensor)
-The Point is just active occasionally so the [Sensors](#sensor) are only updated every hour or so. The [Binary Sensors](#binary-sensor) are however updated via [Cloud Push](https://www.home-assistant.io/blog/2016/02/12/classifying-the-internet-of-things/#cloud-pushing-new-state), making the changes close to instant.
+The Point is just active occasionally so the [Sensors](#sensor) are only updated every hour or so. The [Binary Sensors](#binary-sensor) are however updated via [Cloud Push](/blog/2016/02/12/classifying-the-internet-of-things/#cloud-pushing-new-state), making the changes close to instant.
## Alarm
diff --git a/source/_components/ps4.markdown b/source/_components/ps4.markdown
index 62b9f110f40..83f64747cbe 100644
--- a/source/_components/ps4.markdown
+++ b/source/_components/ps4.markdown
@@ -77,7 +77,7 @@ sudo setcap 'cap_net_bind_service=+ep' /usr/bin/python3.5
To find your system Python path:
-- Add the [System Health](https://www.home-assistant.io/components/system_health/) integration to your `configuration.yaml`. In a web browser access your frontend and navigate to the about/logs page "http:///dev-info). In the System Health box locate the item **python_version** and note the value that is displayed. Then in terminal run:
+- Add the [System Health](/components/system_health/) integration to your `configuration.yaml`. In a web browser access your frontend and navigate to the about/logs page "http:///dev-info). In the System Health box locate the item **python_version** and note the value that is displayed. Then in terminal run:
```bash
whereis python
diff --git a/source/_components/utility_meter.markdown b/source/_components/utility_meter.markdown
index 0d362c0a441..93206e25cb5 100644
--- a/source/_components/utility_meter.markdown
+++ b/source/_components/utility_meter.markdown
@@ -153,7 +153,7 @@ automation:
## Advanced Configuration for DSMR users
-When using the [DSMR component](https://www.home-assistant.io/components/sensor.dsmr/) to get data from the utility meter, each tariff (peak and off-peak) has a separate sensor. Additionally, there is a separate sensor for gas consumption. The meter switches automatically between tariffs, so an automation is not necessary in this case. But, you do have to setup a few more instances of the `utility_meter` component.
+When using the [DSMR component](/components/sensor.dsmr/) to get data from the utility meter, each tariff (peak and off-peak) has a separate sensor. Additionally, there is a separate sensor for gas consumption. The meter switches automatically between tariffs, so an automation is not necessary in this case. But, you do have to setup a few more instances of the `utility_meter` component.
If you want to create a daily and monthly sensor for each tariff, you have to track separate sensors:
diff --git a/source/_docs/ecosystem/haproxy.markdown b/source/_docs/ecosystem/haproxy.markdown
index b62f8ba75f9..628d04bef9f 100644
--- a/source/_docs/ecosystem/haproxy.markdown
+++ b/source/_docs/ecosystem/haproxy.markdown
@@ -95,7 +95,7 @@ Replace 443 with whatever port you chose to bind to in the config if different.
### Configure Home Assistant HTTP Component
-In your `configuration.yaml` file, edit the [http component](https://www.home-assistant.io/components/http/).
+In your `configuration.yaml` file, edit the [http component](/components/http/).
```text
http:
diff --git a/source/_lovelace/picture-entity.markdown b/source/_lovelace/picture-entity.markdown
index 11d09b5f547..30ceb81c2a2 100644
--- a/source/_lovelace/picture-entity.markdown
+++ b/source/_lovelace/picture-entity.markdown
@@ -149,4 +149,4 @@ tap_action:
```
{% endraw %}
-The filename needs to be a path that is writable by Home Assistant in your system. You may need to configure `whitelist_external_dirs` ([documentation](https://www.home-assistant.io/docs/configuration/basic/)).
+The filename needs to be a path that is writable by Home Assistant in your system. You may need to configure `whitelist_external_dirs` ([documentation](/docs/configuration/basic/)).
diff --git a/source/_posts/2018-07-16-release-73-2.markdown b/source/_posts/2018-07-16-release-73-2.markdown
index fdaaae717ba..0965be70a02 100644
--- a/source/_posts/2018-07-16-release-73-2.markdown
+++ b/source/_posts/2018-07-16-release-73-2.markdown
@@ -16,40 +16,40 @@ A man in the middle attack is when an attacker is able to inject itself between
After research, the following integrations have been impacted. Although the odds are extremely small, we still suggest that if you use any of these integrations, to create new API keys or change your password.
-- [alarm_control_panel.alarmdotcom](https://www.home-assistant.io/components/alarm_control_panel.alarmdotcom/)
-- [climate.sensibo](https://www.home-assistant.io/components/climate.sensibo/)
-- [cloud](https://www.home-assistant.io/components/cloud/) (only short lived tokens impacted)
-- [device_tracker.automatic](https://www.home-assistant.io/components/device_tracker.automatic/)
-- [duckdns](https://www.home-assistant.io/components/duckdns/)
-- [freedns](https://www.home-assistant.io/components/freedns/)
-- [google_assistant](https://www.home-assistant.io/components/google_assistant/) (manual setup)
-- [google_domains](https://www.home-assistant.io/components/google_domains/)
-- [homematicip_cloud](https://www.home-assistant.io/components/homematicip_cloud/)
-- [image_processing.openalpr_cloud](https://www.home-assistant.io/components/image_processing.openalpr_cloud/)
-- [microsoft_face](https://www.home-assistant.io/components/microsoft_face/)
-- [namecheapdns](https://www.home-assistant.io/components/namecheapdns/)
-- [no_ip](https://www.home-assistant.io/components/no_ip/)
-- [notify.flock](https://www.home-assistant.io/components/notify.flock/)
-- [notify.prowl](https://www.home-assistant.io/components/notify.prowl/)
-- [rest_command](https://www.home-assistant.io/components/rest_command/)
-- [scene.lifx_cloud](https://www.home-assistant.io/components/scene.lifx_cloud/)
-- [switch.hook](https://www.home-assistant.io/components/switch.hook/)
-- [switch.rest](https://www.home-assistant.io/components/switch.rest/)
-- [telegram_bot.polling](https://www.home-assistant.io/components/telegram_bot.polling/)
-- [tts.voicerss](https://www.home-assistant.io/components/tts.voicerss/)
+- [alarm_control_panel.alarmdotcom](/components/alarm_control_panel.alarmdotcom/)
+- [climate.sensibo](/components/climate.sensibo/)
+- [cloud](/components/cloud/) (only short lived tokens impacted)
+- [device_tracker.automatic](/components/device_tracker.automatic/)
+- [duckdns](/components/duckdns/)
+- [freedns](/components/freedns/)
+- [google_assistant](/components/google_assistant/) (manual setup)
+- [google_domains](/components/google_domains/)
+- [homematicip_cloud](/components/homematicip_cloud/)
+- [image_processing.openalpr_cloud](/components/image_processing.openalpr_cloud/)
+- [microsoft_face](/components/microsoft_face/)
+- [namecheapdns](/components/namecheapdns/)
+- [no_ip](/components/no_ip/)
+- [notify.flock](/components/notify.flock/)
+- [notify.prowl](/components/notify.prowl/)
+- [rest_command](/components/rest_command/)
+- [scene.lifx_cloud](/components/scene.lifx_cloud/)
+- [switch.hook](/components/switch.hook/)
+- [switch.rest](/components/switch.rest/)
+- [telegram_bot.polling](/components/telegram_bot.polling/)
+- [tts.voicerss](/components/tts.voicerss/)
Also impacted, but integrations are read only:
-- [sensor.airvisual](https://www.home-assistant.io/components/sensor.airvisual/)
-- [sensor.ebox](https://www.home-assistant.io/components/sensor.ebox/)
-- [sensor.fido](https://www.home-assistant.io/components/sensor.fido/)
-- [sensor.foobot](https://www.home-assistant.io/components/sensor.foobot/)
-- [sensor.hydroquebec](https://www.home-assistant.io/components/sensor.hydroquebec/)
-- [sensor.startca](https://www.home-assistant.io/components/sensor.startca/)
-- [sensor.teksavvy](https://www.home-assistant.io/components/sensor.teksavvy/)
-- [sensor.thethingsnetwork](https://www.home-assistant.io/components/sensor.thethingsnetwork/)
-- [sensor.tibber](https://www.home-assistant.io/components/sensor.tibber/)
-- [sensor.waqi](https://www.home-assistant.io/components/sensor.waqi/)
+- [sensor.airvisual](/components/sensor.airvisual/)
+- [sensor.ebox](/components/sensor.ebox/)
+- [sensor.fido](/components/sensor.fido/)
+- [sensor.foobot](/components/sensor.foobot/)
+- [sensor.hydroquebec](/components/sensor.hydroquebec/)
+- [sensor.startca](/components/sensor.startca/)
+- [sensor.teksavvy](/components/sensor.teksavvy/)
+- [sensor.thethingsnetwork](/components/sensor.thethingsnetwork/)
+- [sensor.tibber](/components/sensor.tibber/)
+- [sensor.waqi](/components/sensor.waqi/)
If you are running Home Assistant on a system with Python 3.4, we've created a new release 0.64.4b0 with the patch applied. We have made it available as a beta. To install the pre-release run `python3 -m pip install homeassistant==0.64.4b0`.
@@ -59,48 +59,48 @@ For complete transparency, the following two sets of integrations also used aioh
Affected, but not transmitting authentication:
-- [sensor.buienradar](https://www.home-assistant.io/components/sensor.buienradar/)
-- [sensor.citybikes](https://www.home-assistant.io/components/sensor.citybikes/)
-- [sensor.comed_hourly_pricing](https://www.home-assistant.io/components/sensor.comed_hourly_pricing/)
-- [sensor.luftdaten](https://www.home-assistant.io/components/sensor.luftdaten/)
-- [sensor.pollen](https://www.home-assistant.io/components/sensor.pollen/)
-- [sensor.sochain](https://www.home-assistant.io/components/sensor.sochain/)
-- [sensor.swiss_public_transport](https://www.home-assistant.io/components/sensor.swiss_public_transport/)
-- [sensor.viaggiatreno](https://www.home-assistant.io/components/sensor.viaggiatreno/)
-- [sensor.wunderground](https://www.home-assistant.io/components/sensor.wunderground/)
-- [sensor.yr](https://www.home-assistant.io/components/sensor.yr/)
-- [weather.ipma](https://www.home-assistant.io/components/weather.ipma/)
-- [tts.google](https://www.home-assistant.io/components/tts.google/)
-- [tts.yandextts](https://www.home-assistant.io/components/tts.yandextts/)
-- [updater](https://www.home-assistant.io/components/updater/)
+- [sensor.buienradar](/components/sensor.buienradar/)
+- [sensor.citybikes](/components/sensor.citybikes/)
+- [sensor.comed_hourly_pricing](/components/sensor.comed_hourly_pricing/)
+- [sensor.luftdaten](/components/sensor.luftdaten/)
+- [sensor.pollen](/components/sensor.pollen/)
+- [sensor.sochain](/components/sensor.sochain/)
+- [sensor.swiss_public_transport](/components/sensor.swiss_public_transport/)
+- [sensor.viaggiatreno](/components/sensor.viaggiatreno/)
+- [sensor.wunderground](/components/sensor.wunderground/)
+- [sensor.yr](/components/sensor.yr/)
+- [weather.ipma](/components/weather.ipma/)
+- [tts.google](/components/tts.google/)
+- [tts.yandextts](/components/tts.yandextts/)
+- [updater](/components/updater/)
Local, so cannot be impacted:
-- [android_ip_webcam](https://www.home-assistant.io/components/android_ip_webcam/)
-- [apple_tv](https://www.home-assistant.io/components/apple_tv/)
-- [camera.amcrest](https://www.home-assistant.io/components/camera.amcrest/)
-- [camera.doorbird](https://www.home-assistant.io/components/camera.doorbird/)
-- [camera.familyhub](https://www.home-assistant.io/components/camera.familyhub/)
-- [camera.generic](https://www.home-assistant.io/components/camera.generic/)
-- [camera.mjpeg](https://www.home-assistant.io/components/camera.mjpeg/)
-- [camera.proxy](https://www.home-assistant.io/components/camera.proxy/)
-- [camera.synology](https://www.home-assistant.io/components/camera.synology/)
-- [deconz](https://www.home-assistant.io/components/deconz/)
-- [device_tracker.upc_connect](https://www.home-assistant.io/components/device_tracker.upc_connect/)
-- [hassio](https://www.home-assistant.io/components/hassio/)
-- [hue](https://www.home-assistant.io/components/hue/)
-- [media_player.bluesound](https://www.home-assistant.io/components/media_player.bluesound/)
-- [media_player.epson](https://www.home-assistant.io/components/media_player.epson/)
-- [media_player.kodi](https://www.home-assistant.io/components/media_player.kodi/)
-- [media_player.squeezebox](https://www.home-assistant.io/components/media_player.squeezebox/)
-- [media_player.volumio](https://www.home-assistant.io/components/media_player.volumio/)
-- [notify.kodi](https://www.home-assistant.io/components/notify.kodi/)
-- [qwikswitch](https://www.home-assistant.io/components/qwikswitch/)
-- [rainmachine](https://www.home-assistant.io/components/rainmachine/)
-- [scene.hunterdouglas_powerview](https://www.home-assistant.io/components/scene.hunterdouglas_powerview/)
-- [sensor.netdata](https://www.home-assistant.io/components/sensor.netdata/)
-- [sensor.pi_hole](https://www.home-assistant.io/components/sensor.pi_hole/)
-- [sensor.sma](https://www.home-assistant.io/components/sensor.sma/)
-- [sensor.worxlandroid](https://www.home-assistant.io/components/sensor.worxlandroid/)
-- [spc](https://www.home-assistant.io/components/spc/)
-- [tts.marytts](https://www.home-assistant.io/components/tts.marytts/)
+- [android_ip_webcam](/components/android_ip_webcam/)
+- [apple_tv](/components/apple_tv/)
+- [camera.amcrest](/components/camera.amcrest/)
+- [camera.doorbird](/components/camera.doorbird/)
+- [camera.familyhub](/components/camera.familyhub/)
+- [camera.generic](/components/camera.generic/)
+- [camera.mjpeg](/components/camera.mjpeg/)
+- [camera.proxy](/components/camera.proxy/)
+- [camera.synology](/components/camera.synology/)
+- [deconz](/components/deconz/)
+- [device_tracker.upc_connect](/components/device_tracker.upc_connect/)
+- [hassio](/components/hassio/)
+- [hue](/components/hue/)
+- [media_player.bluesound](/components/media_player.bluesound/)
+- [media_player.epson](/components/media_player.epson/)
+- [media_player.kodi](/components/media_player.kodi/)
+- [media_player.squeezebox](/components/media_player.squeezebox/)
+- [media_player.volumio](/components/media_player.volumio/)
+- [notify.kodi](/components/notify.kodi/)
+- [qwikswitch](/components/qwikswitch/)
+- [rainmachine](/components/rainmachine/)
+- [scene.hunterdouglas_powerview](/components/scene.hunterdouglas_powerview/)
+- [sensor.netdata](/components/sensor.netdata/)
+- [sensor.pi_hole](/components/sensor.pi_hole/)
+- [sensor.sma](/components/sensor.sma/)
+- [sensor.worxlandroid](/components/sensor.worxlandroid/)
+- [spc](/components/spc/)
+- [tts.marytts](/components/tts.marytts/)
diff --git a/source/_posts/2018-09-17-thinking-big.markdown b/source/_posts/2018-09-17-thinking-big.markdown
index dfd755524a6..d2ccf91bd13 100644
--- a/source/_posts/2018-09-17-thinking-big.markdown
+++ b/source/_posts/2018-09-17-thinking-big.markdown
@@ -80,7 +80,7 @@ Relying on donations makes budgeting for employees impossible without exposing t
### Is Home Assistant Cloud open source?
-The majority of Home Assistant Cloud is open source. The Alexa skill source code is [here](https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/alexa/smart_home.py) (with manual setup instructions [here](https://github.com/mike-grant/haaska/)) and the Google Assistant source code is [here](https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/google_assistant/smart_home.py) (with manual setup instructions [here](https://www.home-assistant.io/components/google_assistant/)). Our account page and relayer are not open source.
+The majority of Home Assistant Cloud is open source. The Alexa skill source code is [here](https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/alexa/smart_home.py) (with manual setup instructions [here](https://github.com/mike-grant/haaska/)) and the Google Assistant source code is [here](https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/google_assistant/smart_home.py) (with manual setup instructions [here](/components/google_assistant/)). Our account page and relayer are not open source.
### Will you offer a lifetime plan for a one time fee?
diff --git a/source/_posts/2018-09-30-hacktoberfest.markdown b/source/_posts/2018-09-30-hacktoberfest.markdown
index cc80e124d26..aa3e6669e27 100644
--- a/source/_posts/2018-09-30-hacktoberfest.markdown
+++ b/source/_posts/2018-09-30-hacktoberfest.markdown
@@ -81,5 +81,5 @@ If you think that you are not enough qualified to do it, don’t worry, there ar
## Not a coder? Not a problem!
-Also, feel free to [report bugs](https://github.com/home-assistant/home-assistant/issues/new/choose), give us feedback about your user experience, tell the community about your [super cool setup](https://community.home-assistant.io/c/projects), create a [super awesome frontend](https://community.home-assistant.io/c/projects/frontend) with [Lovelace](https://www.home-assistant.io/lovelace) or help other users in the [forum](https://community.home-assistant.io/).
+Also, feel free to [report bugs](https://github.com/home-assistant/home-assistant/issues/new/choose), give us feedback about your user experience, tell the community about your [super cool setup](https://community.home-assistant.io/c/projects), create a [super awesome frontend](https://community.home-assistant.io/c/projects/frontend) with [Lovelace](/lovelace) or help other users in the [forum](https://community.home-assistant.io/).
diff --git a/source/_posts/2018-10-12-release-80.markdown b/source/_posts/2018-10-12-release-80.markdown
index d7e381a596d..9f2df06316a 100644
--- a/source/_posts/2018-10-12-release-80.markdown
+++ b/source/_posts/2018-10-12-release-80.markdown
@@ -98,10 +98,10 @@ On the devices side, we got basic support for the new IKEA TRÅDFRI switches, Ho
[@StevenLooman]: https://github.com/StevenLooman
[@balloob]: https://github.com/balloob
[@hobbypunk90]: https://github.com/hobbypunk90
-[hangouts docs]: https://www.home-assistant.io/components/hangouts/
-[media_player.dlna_dmr docs]: https://www.home-assistant.io/components/media_player.dlna_dmr/
-[media_player.snapcast docs]: https://www.home-assistant.io/components/media_player.snapcast/
-[upnp docs]: https://www.home-assistant.io/components/upnp/
+[hangouts docs]: /components/hangouts/
+[media_player.dlna_dmr docs]: /components/media_player.dlna_dmr/
+[media_player.snapcast docs]: /components/media_player.snapcast/
+[upnp docs]: /components/upnp/
## New Features
diff --git a/source/_posts/2018-10-29-release-81.markdown b/source/_posts/2018-10-29-release-81.markdown
index 8e370912db4..e06fdfd3a55 100644
--- a/source/_posts/2018-10-29-release-81.markdown
+++ b/source/_posts/2018-10-29-release-81.markdown
@@ -866,4 +866,4 @@ Experiencing issues introduced by this release? Please report them in our [issue
[zha docs]: /components/zha/
[zoneminder docs]: /components/zoneminder/
[zwave docs]: /components/zwave/
-[platform_options]: https://www.home-assistant.io/docs/configuration/platform_options/#scan-interval
+[platform_options]: /docs/configuration/platform_options/#scan-interval
diff --git a/source/_posts/2018-12-17-logitech-harmony-removes-local-api.markdown b/source/_posts/2018-12-17-logitech-harmony-removes-local-api.markdown
index c723955d438..217ffdaaf38 100644
--- a/source/_posts/2018-12-17-logitech-harmony-removes-local-api.markdown
+++ b/source/_posts/2018-12-17-logitech-harmony-removes-local-api.markdown
@@ -52,7 +52,7 @@ We hope that this was an oversight on their end and that it will be reverted sho
Thread by member of the Harmony Team.
-**Update 3 (18 dec):** Twitter user [@ChadBeattie](https://twitter.com/ChadBeattie/status/1074770135121125376) has discovered that there seems to be a second undocumented local API that is being used by the Logitech Harmony iOS app. Home Assistant developer [@ehendrix23] is looking into updating the PyHarmony library to use this. Join #devs_backend on [our chat](https://www.home-assistant.io/join-chat/) if you want to help with development. We can't guarantee that it will work, but if we can get it to work, we will do a hot fix release.
+**Update 3 (18 dec):** Twitter user [@ChadBeattie](https://twitter.com/ChadBeattie/status/1074770135121125376) has discovered that there seems to be a second undocumented local API that is being used by the Logitech Harmony iOS app. Home Assistant developer [@ehendrix23] is looking into updating the PyHarmony library to use this. Join #devs_backend on [our chat](/join-chat/) if you want to help with development. We can't guarantee that it will work, but if we can get it to work, we will do a hot fix release.
[@ehendrix23]: https://github.com/ehendrix23
diff --git a/source/_posts/2019-01-23-lovelace-released.markdown b/source/_posts/2019-01-23-lovelace-released.markdown
index 8efcd1d3ada..0145bf6527f 100644
--- a/source/_posts/2019-01-23-lovelace-released.markdown
+++ b/source/_posts/2019-01-23-lovelace-released.markdown
@@ -13,7 +13,7 @@ og_image: /images/blog/2019-01-lovelace/demo.png
Today we're happy to announce that our new Lovelace UI, which has been in beta for the last 8 months, is becoming the new default interface of [Home Assistant 0.86](/blog/2019/01/23/release-86/). With Lovelace we're taking a new approach to building user interfaces for Home Assistant. We're no longer storing the look and feel of your UI in your configuration.yaml, requiring restarts for changes. With Lovelace we're keeping the UI concerns in the UI1, unlocking a whole new set of features:
- - [24 cards](https://www.home-assistant.io/lovelace/alarm-panel/) to place and configure as you like.
+ - [24 cards](/lovelace/alarm-panel/) to place and configure as you like.
- UI Editor. A configuration UI to manage your Lovelace UI including live preview when editing cards.
- Fast. Using a static config allows us to build up the UI once.
- Customizable.
diff --git a/source/_posts/2019-02-11-hass-cli-0-dot-5-area-entity-registry-and-event-cli.markdown b/source/_posts/2019-02-11-hass-cli-0-dot-5-area-entity-registry-and-event-cli.markdown
index ec4a6e0ff50..9f0766e770d 100644
--- a/source/_posts/2019-02-11-hass-cli-0-dot-5-area-entity-registry-and-event-cli.markdown
+++ b/source/_posts/2019-02-11-hass-cli-0-dot-5-area-entity-registry-and-event-cli.markdown
@@ -154,4 +154,4 @@ Have fun!
[@maxandersen]: https://xam.dk/about
-[hass-087]: https://www.home-assistant.io/blog/2019/02/06/release-87/
+[hass-087]: /blog/2019/02/06/release-87/
diff --git a/source/_posts/2019-03-20-release-90.markdown b/source/_posts/2019-03-20-release-90.markdown
index d7cffa52260..704cc499bd2 100644
--- a/source/_posts/2019-03-20-release-90.markdown
+++ b/source/_posts/2019-03-20-release-90.markdown
@@ -140,13 +140,13 @@ Experiencing issues introduced by this release? Please report them in our [issue
## Breaking Changes
-- __http.api_password__ - __Deprecated__ - Users who are still using api_password for authentication will need to move its configuration under auth_providers. Please see the [updated documentation](https://www.home-assistant.io/docs/authentication/providers/#legacy-api-password) for further details. Those who don't make this change will see an INFO level reminder in the Home Assistant logs until the fix is made for a time, but please note, __api_password authentication will eventually be removed completely__ and we advise users to change to use one of the [other authentication methods](https://www.home-assistant.io/docs/authentication/providers/#available-auth-providers). If you manually specify auth providers in your `configuration.yaml`, you will need to migrate your API Password from the http section to the auth provider section to continue using it. ([@awarecan] - [#21884]) ([api docs]) ([frontend docs]) ([hassio docs]) ([http docs]) ([mqtt docs]) ([websocket_api docs]) ([zeroconf docs]) ([camera.proxy docs])
+- __http.api_password__ - __Deprecated__ - Users who are still using api_password for authentication will need to move its configuration under auth_providers. Please see the [updated documentation](/docs/authentication/providers/#legacy-api-password) for further details. Those who don't make this change will see an INFO level reminder in the Home Assistant logs until the fix is made for a time, but please note, __api_password authentication will eventually be removed completely__ and we advise users to change to use one of the [other authentication methods](/docs/authentication/providers/#available-auth-providers). If you manually specify auth providers in your `configuration.yaml`, you will need to migrate your API Password from the http section to the auth provider section to continue using it. ([@awarecan] - [#21884]) ([api docs]) ([frontend docs]) ([hassio docs]) ([http docs]) ([mqtt docs]) ([websocket_api docs]) ([zeroconf docs]) ([camera.proxy docs])
- __Default Config__ - Default config no longer contains the discovery component. That is now part of the initial written configuration.yaml. If you rely on default config and want to use discovery, add `discovery:` back to your configuration.yaml.
- __Netatmo__
- * Added support for multiple Netatmo thermostats/valves allowing the user to specify different homes or rooms! Please check the [updated documentation](https://www.home-assistant.io/components/climate.netatmo/) for configuration details. ([@shanbs] - [#19407]) ([netatmo docs]) ([climate.netatmo docs])
- * `current_operation` will no longer return the the boiler status, but the operation_mode. For example, heat, cool, or idle. Please check the [updated documentation](https://www.home-assistant.io/components/climate.netatmo/) for more details. ([@shanbs] - [#21633]) ([netatmo docs])
+ * Added support for multiple Netatmo thermostats/valves allowing the user to specify different homes or rooms! Please check the [updated documentation](/components/climate.netatmo/) for configuration details. ([@shanbs] - [#19407]) ([netatmo docs]) ([climate.netatmo docs])
+ * `current_operation` will no longer return the the boiler status, but the operation_mode. For example, heat, cool, or idle. Please check the [updated documentation](/components/climate.netatmo/) for more details. ([@shanbs] - [#21633]) ([netatmo docs])
- __Utility Meter__ - Currently the offset configuration parameter is an integer that limits daily cycles to have offsets in days, monthly cycles to have offsets in months, etc.
-This change increases the flexibility of offset by making it a more flexible time period that can be described in a combination of hours, days, months, etc. This makes it possible for a yearly cycle to start at a given day of a given month. Please see the [updated documentation](https://www.home-assistant.io/components/utility_meter/) for the new configuration options. ([@dgomes] - [#20926]) ([utility_meter docs])
+This change increases the flexibility of offset by making it a more flexible time period that can be described in a combination of hours, days, months, etc. This makes it possible for a yearly cycle to start at a given day of a given month. Please see the [updated documentation](/components/utility_meter/) for the new configuration options. ([@dgomes] - [#20926]) ([utility_meter docs])
- __KNX__ - An update for xknx to version 0.10.0 requires users to update their configuration by changing `target_temperature_address` to `target_temperature_state_address`. Other fixes and features:
* Connection config can now be configured in xknx.yml.
* Introduce a configurable rate limit which limits the number of KNX telegrams sent to the bus per second.
diff --git a/source/_posts/2019-04-01-android.markdown b/source/_posts/2019-04-01-android.markdown
index b5496d5343a..f7a724aa928 100644
--- a/source/_posts/2019-04-01-android.markdown
+++ b/source/_posts/2019-04-01-android.markdown
@@ -10,7 +10,7 @@ comments: true
categories: Announcements
---
-1 year, 11 months and 17 days ago or 716 days ago, [I announced Home Assistant Companion for iOS on this blog](https://www.home-assistant.io/blog/2017/04/15/ios/).
+1 year, 11 months and 17 days ago or 716 days ago, [I announced Home Assistant Companion for iOS on this blog](/blog/2017/04/15/ios/).
Ever since then, at least once a week, sometimes far more often, I am asked a question that I haven't been able to truly answer until today.
It's a question that has gotten on my nerves almost every time I've seen it. I could understand why people were wanting an official Android app to mirror the functionality of the iOS app.
But I never thought of myself as the person to best deliver on that idea.
diff --git a/source/_posts/2019-04-03-release-91.markdown b/source/_posts/2019-04-03-release-91.markdown
index 18bd8d61ba6..24a77cf6c67 100644
--- a/source/_posts/2019-04-03-release-91.markdown
+++ b/source/_posts/2019-04-03-release-91.markdown
@@ -203,8 +203,8 @@ Experiencing issues introduced by this release? Please report them in our [issue
- __iOS__ - Improves the text description of ATTR_BATTERY_STATE_UNPLUGGED from Unplugged to Not Charging as many new iOS devices now use Wireless charging and there is no concept of "Plugging In". This is potentially a breaking change if you have automations making use of "unplugged". ([@FattusMannus] - [#22152]) ([ios docs])
- __Iliad Italy__ - __Removed__ - This was removed because it uses webscraping. ([@eliseomartelli] - [#22175])
-- __Netgear lte__ - The previous three components (network, notify, and sensor) now fall under one netgear_lte component. Check the [updated documentation](https://www.home-assistant.io/components/netgear_lte/) for more information. ([@amelchio] - [#22105]) ([netgear_lte docs])
-- __API streams sensor__ - __Removed__ - This sensor component was designed to count connected front-end clients. However, it depended on the implementation details of other components, and has therefore been broken since 0.80, so it has been removed. The replacement sensor is now the [websocket_api sensor](https://www.home-assistant.io/components/websocket_api/), which does basically the same thing apart from the rename. ([@Swamp-Ig] - [#22200]) ([websocket_api docs])
+- __Netgear lte__ - The previous three components (network, notify, and sensor) now fall under one netgear_lte component. Check the [updated documentation](/components/netgear_lte/) for more information. ([@amelchio] - [#22105]) ([netgear_lte docs])
+- __API streams sensor__ - __Removed__ - This sensor component was designed to count connected front-end clients. However, it depended on the implementation details of other components, and has therefore been broken since 0.80, so it has been removed. The replacement sensor is now the [websocket_api sensor](/components/websocket_api/), which does basically the same thing apart from the rename. ([@Swamp-Ig] - [#22200]) ([websocket_api docs])
- __Public Transit (GTFS)__
* The state for this sensor component was a countdown in minutes. If the next departure was in a few hours, this number became quite large and a tad harder to rapidly calculate mentally (463 minutes anyone?). The sensor's state output has been changed from minutes to an ISO 8601 UTC timestamp, which allows the UI to interpret the state as needed. ([@renemarc] - [#21053]) ([gtfs docs])
* Sensor updates were running many database queries to populate attributes, on top of the bus schedule queries themselves. This is doubled with two sensors. That led to a lot of slowdowns for everything else when using an SD card! Considering that some data never changes (agency, routes...) and that others like departure times are good until invalidated, now we fetch such metadata at first and then only when relevant changes do occur. GTFS sensor attributes are now named using the standard snake_case format. ([@renemarc] - [#20966]) ([gtfs docs])
diff --git a/source/_posts/2019-04-15-hassio-ingress.markdown b/source/_posts/2019-04-15-hassio-ingress.markdown
index 7f185a03df8..3892cd28f9c 100644
--- a/source/_posts/2019-04-15-hassio-ingress.markdown
+++ b/source/_posts/2019-04-15-hassio-ingress.markdown
@@ -23,7 +23,7 @@ Demo with an add-on on Ingress.
Some add-ons already have been upgraded to support the new Ingress feature. Here are a couple of add-ons that support Ingress and are available on the add-on store right now:
Core add-ons:
-* [Configurator](https://www.home-assistant.io/addons/configurator/)
+* [Configurator](/addons/configurator/)
* [deCONZ](https://github.com/home-assistant/hassio-addons/tree/master/deconz#readme)
Community add-ons:
@@ -78,7 +78,7 @@ Please update your Home Assistant installation to 0.91.3 or higher.
We found a last minute issue impacting Firefox based browsers (including the Tor Browser). There are some issues accessing add-ons that use WebSockets. We have identified the issue and expect it to be solved with the release of Home Assistant 0.91.4.
-[Configurator]: https://www.home-assistant.io/addons/configurator/
+[Configurator]: /addons/configurator/
[deCONZ]: https://github.com/home-assistant/hassio-addons/tree/master/deconz#readme
[Node-RED]: https://github.com/hassio-addons/addon-node-red#readme
[Visual Studio Code]: https://github.com/hassio-addons/addon-vscode#readme
diff --git a/source/_posts/2019-04-24-release-92.markdown b/source/_posts/2019-04-24-release-92.markdown
index 80ed2f74206..82a78a20d27 100644
--- a/source/_posts/2019-04-24-release-92.markdown
+++ b/source/_posts/2019-04-24-release-92.markdown
@@ -143,19 +143,19 @@ Finally, if you are still receiving a message that your configuration contains e
[@pvizeli]: https://github.com/pvizeli
[@robbiet480]: https://github.com/robbiet480
[@zxdavb]: https://github.com/zxdavb
-[alexa docs]: https://www.home-assistant.io/components/alexa/
-[auth docs]: https://www.home-assistant.io/components/auth/
-[cast docs]: https://www.home-assistant.io/components/cast/
-[cloud docs]: https://www.home-assistant.io/components/cloud/
-[geniushub docs]: https://www.home-assistant.io/components/geniushub/
-[google_assistant docs]: https://www.home-assistant.io/components/google_assistant/
-[heos docs]: https://www.home-assistant.io/components/heos/
-[hue docs]: https://www.home-assistant.io/components/hue/
-[mobile_app docs]: https://www.home-assistant.io/components/mobile_app/
-[myq docs]: https://www.home-assistant.io/components/myq/
-[netatmo_public docs]: https://www.home-assistant.io/components/netatmo_public/
-[traccar docs]: https://www.home-assistant.io/components/traccar/
-[upnp docs]: https://www.home-assistant.io/components/upnp/
+[alexa docs]: /components/alexa/
+[auth docs]: /components/auth/
+[cast docs]: /components/cast/
+[cloud docs]: /components/cloud/
+[geniushub docs]: /components/geniushub/
+[google_assistant docs]: /components/google_assistant/
+[heos docs]: /components/heos/
+[hue docs]: /components/hue/
+[mobile_app docs]: /components/mobile_app/
+[myq docs]: /components/myq/
+[netatmo_public docs]: /components/netatmo_public/
+[traccar docs]: /components/traccar/
+[upnp docs]: /components/upnp/
## If you need help...
diff --git a/source/_posts/2019-05-03-update-from-the-field.markdown b/source/_posts/2019-05-03-update-from-the-field.markdown
index 59d8ce50bc2..521c36b42c2 100644
--- a/source/_posts/2019-05-03-update-from-the-field.markdown
+++ b/source/_posts/2019-05-03-update-from-the-field.markdown
@@ -33,7 +33,7 @@ This month marked a year since Ubiquiti got involved, and also their last month,
For the last year, the Home Assistant community has been working on building a user-friendly version of Home Assistant, also known as Home Assistant 1.0.
-We’re aiming to release Home Assistant 1.0 this year. With Home Assistant 1.0, installation and basic functionality can be done via a user interface. Advanced options will require entering an advanced mode or set up via `configuration.yaml`. Check out last year’s [state of the union](https://www.home-assistant.io/blog/2018/11/16/state-of-the-union/) for more details. We have started using [this project board](https://github.com/orgs/home-assistant/projects/1) to keep track of our progress.
+We’re aiming to release Home Assistant 1.0 this year. With Home Assistant 1.0, installation and basic functionality can be done via a user interface. Advanced options will require entering an advanced mode or set up via `configuration.yaml`. Check out last year’s [state of the union](/blog/2018/11/16/state-of-the-union/) for more details. We have started using [this project board](https://github.com/orgs/home-assistant/projects/1) to keep track of our progress.
While we’re working hard on Home Assistant 1.0, we have also started working on the next goal for post 1.0 launch: a better story for manufacturers and integrations.
diff --git a/source/_posts/2019-06-26-release-95.markdown b/source/_posts/2019-06-26-release-95.markdown
index a5f7a92a91d..c503dd9db97 100644
--- a/source/_posts/2019-06-26-release-95.markdown
+++ b/source/_posts/2019-06-26-release-95.markdown
@@ -53,7 +53,7 @@ If you are migrating from the custom integration, [please read the instructions]
One more thing… This release improves the Home Assistant Cloud Alexa integration. Just like Google Assistant, it is now possible to manage which entities are exposed to Amazon via the user interface. Alexa actually offers some cool features around this. Any change you make is instantly reflected inside Alexa. Add an entity? Control it instantly via Alexa.
-However, we didn't stop there. The [manual installations of Alexa](https://www.home-assistant.io/components/alexa.smart_home/#alexa-component-configuration) has had optional proactive state reporting since earlier this year, and this is now available for Home Assistant Cloud users too. If you choose to opt-in to this, every state change of your exposed entities is sent to Amazon as soon as they happen. It allows Amazon Echos with displays, to instantly reflect the state and allows you to create routines inside Amazon powered by your Home Assistant entities.
+However, we didn't stop there. The [manual installations of Alexa](/components/alexa.smart_home/#alexa-component-configuration) has had optional proactive state reporting since earlier this year, and this is now available for Home Assistant Cloud users too. If you choose to opt-in to this, every state change of your exposed entities is sent to Amazon as soon as they happen. It allows Amazon Echos with displays, to instantly reflect the state and allows you to create routines inside Amazon powered by your Home Assistant entities.
From 0541dbd6e369adb283391e22be3606df19055502 Mon Sep 17 00:00:00 2001
From: aidbish <38182386+aidbish@users.noreply.github.com>
Date: Sat, 6 Jul 2019 17:12:58 +1000
Subject: [PATCH 03/44] Fix Broken links (#9793)
* Fix VLC and ELV broken links
relates to https://github.com/home-assistant/home-assistant.io/issues/9774
* Removed references to Uber Docs
* Updated broken DTE Website link
relates to https://github.com/home-assistant/home-assistant.io/issues/9774
* Removed Snips article
Article no longer available on Medium.com
* Update weblink to product page
relates to https://github.com/home-assistant/home-assistant.io/issues/9774
* Fixed weblink - environment Canada
relates to https://github.com/home-assistant/home-assistant.io/issues/9774
* Updated broken links - GNTP
relates to https://github.com/home-assistant/home-assistant.io/issues/9774
* Update broken links - nuheat
relates to https://github.com/home-assistant/home-assistant.io/issues/9774
* Update DS18S20 broken link
relates to https://github.com/home-assistant/home-assistant.io/issues/9774
---
source/_components/dte_energy_bridge.markdown | 2 +-
source/_components/enphase_envoy.markdown | 2 +-
source/_components/environment_canada.markdown | 2 +-
source/_components/gntp.markdown | 2 +-
source/_components/nuheat.markdown | 2 +-
source/_components/onewire.markdown | 2 +-
source/_posts/2019-06-26-release-95.markdown | 9 ++++-----
source/help/index.markdown | 1 -
8 files changed, 10 insertions(+), 12 deletions(-)
diff --git a/source/_components/dte_energy_bridge.markdown b/source/_components/dte_energy_bridge.markdown
index 3af953f521e..dee796743d2 100644
--- a/source/_components/dte_energy_bridge.markdown
+++ b/source/_components/dte_energy_bridge.markdown
@@ -16,7 +16,7 @@ redirect_from:
- /components/sensor.dte_energy_bridge/
---
-A sensor platform for the [DTE](https://www.dteenergy.com/) Energy Bridge. To find out which version of the DTE Energy Bridge sensor you have, find the status LED on your box.
+A sensor platform for the [DTE](https://www.newlook.dteenergy.com/) Energy Bridge. To find out which version of the DTE Energy Bridge sensor you have, find the status LED on your box.
- If the status LED is on the top, you have a v1.
- If the status LED is on the front, you have a v2.
diff --git a/source/_components/enphase_envoy.markdown b/source/_components/enphase_envoy.markdown
index 26409c14ff6..19534fe8302 100644
--- a/source/_components/enphase_envoy.markdown
+++ b/source/_components/enphase_envoy.markdown
@@ -16,7 +16,7 @@ redirect_from:
- /components/sensor.enphase_envoy/
---
-A sensor platform for the [Enphase Envoy](https://enphase.com/en-us/products-and-services/envoy) solar energy gateway. Works with older models that only have production metrics (ie. Envoy-C) and newer models that offer both production and consumption metrics (ie. Envoy-S).
+A sensor platform for the [Enphase Envoy](https://enphase.com/en-us/products-and-services/envoy-and-combiner) solar energy gateway. Works with older models that only have production metrics (ie. Envoy-C) and newer models that offer both production and consumption metrics (ie. Envoy-S).
### Configuration
diff --git a/source/_components/environment_canada.markdown b/source/_components/environment_canada.markdown
index 40c74f709f7..79cec29d961 100644
--- a/source/_components/environment_canada.markdown
+++ b/source/_components/environment_canada.markdown
@@ -16,7 +16,7 @@ ha_release: 0.95
ha_iot_class: Cloud Polling
---
-The `environment_canada` weather platforms provide meteorological data for Canadian locations from [Environment Canada](hhttps://weather.gc.ca/index_e.html).
+The `environment_canada` weather platforms provide meteorological data for Canadian locations from [Environment Canada](https://weather.gc.ca/index_e.html).
The following device types and data are supported:
diff --git a/source/_components/gntp.markdown b/source/_components/gntp.markdown
index 8b0357ca4b3..3fcde360366 100644
--- a/source/_components/gntp.markdown
+++ b/source/_components/gntp.markdown
@@ -15,7 +15,7 @@ redirect_from:
- /components/notify.gntp/
---
-[GNTP](http://www.growlforwindows.com/gfw/help/gntp.aspx) is a specification for sending and receiving notifications between computers. The most well known server implementations are [Growl](http://growl.info) for Mac and [Growl for Windows](http://www.growlforwindows.com/gfw/).
+[GNTP](http://growl.info/documentation/developer/gntp.php) is a specification for sending and receiving notifications between computers. The most well known server implementations are [Growl](http://growl.info) for Mac and [Growl for Windows](http://www.growlforwindows.com/).
To use GNTP notifications, add the following to your `configuration.yaml` file:
diff --git a/source/_components/nuheat.markdown b/source/_components/nuheat.markdown
index cee7f13126c..93d6006feac 100644
--- a/source/_components/nuheat.markdown
+++ b/source/_components/nuheat.markdown
@@ -16,7 +16,7 @@ redirect_from:
- /components/climate.nuheat/
---
-The `nuheat` integration lets control your connected [NuHeat Signature]([NuHeat Signature](http://www.nuheat.com/products/thermostats/signature-thermostat)) floor heating thermostats from [NuHeat](http://www.nuheat.com/).
+The `nuheat` integration lets control your connected [NuHeat Signature](http://www.nuheat.com/products/thermostats/signature-thermostat) floor heating thermostats from [NuHeat](http://www.nuheat.com/).
There is currently support for the following device types within Home Assistant:
diff --git a/source/_components/onewire.markdown b/source/_components/onewire.markdown
index cb2d92857ad..7cacfeb3d59 100644
--- a/source/_components/onewire.markdown
+++ b/source/_components/onewire.markdown
@@ -21,7 +21,7 @@ The `onewire` platform supports sensors which are using the One wire (1-wire) bu
Supported devices:
- [DS18B20](https://datasheets.maximintegrated.com/en/ds/DS18B20.pdf)
-- [DS18S20](https://www.maximintegrated.com/en/products/analog/sensors-and-sensor-interface/DS18S20.html)
+- [DS18S20](https://www.maximintegrated.com/en/products/sensors/DS18S20.html)
- [DS1822](https://datasheets.maximintegrated.com/en/ds/DS1822.pdf)
- [DS1825](https://datasheets.maximintegrated.com/en/ds/DS1825.pdf)
- [DS28EA00](https://datasheets.maximintegrated.com/en/ds/DS28EA00.pdf) temperature sensors
diff --git a/source/_posts/2019-06-26-release-95.markdown b/source/_posts/2019-06-26-release-95.markdown
index c503dd9db97..6e490b80942 100644
--- a/source/_posts/2019-06-26-release-95.markdown
+++ b/source/_posts/2019-06-26-release-95.markdown
@@ -176,7 +176,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
- Remove binary sensors for ZHA remotes and controllers ([@dmulcahey] - [#24370]) ([zha docs]) (breaking change)
- Restore automation last_triggered with initial_state override ([@frenck] - [#24400]) ([automation docs]) (breaking change)
- Fix recorder defaults ([@balloob] - [#24399]) ([recorder docs]) (breaking change)
-- Uber API is going away on June 13, 2019, remove component ([@robbiet480] - [#24468]) ([uber docs]) (breaking change)
+- Uber API is going away on June 13, 2019, remove component ([@robbiet480] - [#24468]) (breaking change)
- Add Linky sensors : yesterday + months + years ([@Quentame] - [#23726]) ([linky docs]) (breaking change)
- Position is reversed for horizontal awnings ([@kbickar] - [#23257]) ([tahoma docs]) (breaking change)
- Remove conversation from default config ([@balloob] - [#24515]) ([default_config docs]) (breaking change)
@@ -301,7 +301,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
- Life360: Fix config entry handling for accounts imported from configuration ([@pnbruckner] - [#24455]) ([life360 docs])
- Add default config to constaint file ([@balloob] - [#24423])
- Add websock command to query device for triggers ([@emontnemery] - [#24044]) ([automation docs]) ([light docs])
-- Uber API is going away on June 13, 2019, remove component ([@robbiet480] - [#24468]) ([uber docs]) (breaking change)
+- Uber API is going away on June 13, 2019, remove component ([@robbiet480] - [#24468]) (breaking change)
- Use met.no instead of yr.no in default config ([@thomasloven] - [#24470])
- Bump pyubee to 0.7 to support more models ([@mzdrale] - [#24477]) ([ubee docs])
- Somfy open api ([@tetienne] - [#19548]) ([somfy docs]) (new-platform)
@@ -715,7 +715,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[discovery docs]: /components/discovery/
[dlib_face_identify docs]: /components/dlib_face_identify/
[ebusd docs]: /components/ebusd/
-[elv docs]: /components/elv/
+[elv docs]: /components/switch.pca/
[environment_canada docs]: /components/environment_canada/
[esphome docs]: /components/esphome/
[frontend docs]: /components/frontend/
@@ -783,12 +783,11 @@ Experiencing issues introduced by this release? Please report them in our [issue
[traccar docs]: /components/traccar/
[tradfri docs]: /components/tradfri/
[ubee docs]: /components/ubee/
-[uber docs]: /components/uber/
[unifi docs]: /components/unifi/
[velbus docs]: /components/velbus/
[velux docs]: /components/velux/
[vera docs]: /components/vera/
-[vlc_telnet docs]: /components/vlc_telnet/
+[vlc_telnet docs]: /components/vlc-telnet/
[waze_travel_time docs]: /components/waze_travel_time/
[webostv docs]: /components/webostv/
[websocket_api docs]: /components/websocket_api/
diff --git a/source/help/index.markdown b/source/help/index.markdown
index 6bd8199033c..fba3360979d 100644
--- a/source/help/index.markdown
+++ b/source/help/index.markdown
@@ -74,7 +74,6 @@ Don't miss the regular [Home Assistant podcasts](https://hasspodcast.io/).
- [Smart Home Home Assistant Konfiguration mit YAML](http://onesmarthome.de/smart-home-home-assistant-konfiguration/) - July 2017
- [Why can't we have the Internet of Nice Things?](https://opensource.com/article/17/7/home-automation-primer) - July 2017
- [Smart Home Home Assistant Raspberry Pi Installation Hassbian](http://onesmarthome.de/smart-home-home-assistant-raspberry-pi-installation-hassbian/) - July 2017
-- [Integrating Snips with Home Assistant](https://medium.com/snips-ai/integrating-snips-with-home-assistant-314723645c77) - June 2017
- [Jupiter Broadcasting - No Privacy Compromise Home Automation](http://www.jupiterbroadcasting.com/115566/no-privacy-compromise-home-automation/) - June 2017
- [Monitor IoT devices with Home Assistant and Datadog](https://www.datadoghq.com/blog/monitor-home-assistant/) - June 2017
- [Castálio Podcast - Episódio 102: Marcelo Mello - Red Hat e Automação Residencial com Home Assistant](https://youtu.be/hZq8ucpzjCs) - May 2017
From a69a416657c6136fb8b50ad3ed18b601d64dec46 Mon Sep 17 00:00:00 2001
From: aidbish <38182386+aidbish@users.noreply.github.com>
Date: Sat, 6 Jul 2019 17:14:16 +1000
Subject: [PATCH 04/44] Updated release cycle information (#9784)
* Update Release Cycle notes
Updated release cycle information from two weeks to three. Also added small information about betas
* Updated to include HA dev website
Added information about release schedule on HA dev site
---
source/_faq/release.markdown | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/source/_faq/release.markdown b/source/_faq/release.markdown
index f109e5468d0..1c8b5f84082 100644
--- a/source/_faq/release.markdown
+++ b/source/_faq/release.markdown
@@ -10,5 +10,10 @@ footer: true
ha_category: Common
---
-The usual release cycle is two weeks. Every other weekend will a new release of Home Assistant be available. There is no fix day or time when the release will happen because that depends on the person who is finishing the release. It can already be Monday at your location. If there was no announcement made in the previous release notes or on another communication channel then the release will happen.
+The current release cycle is three weeks. This allows for two weeks of development time and 1 week of beta testing and fixing. Releases usually occur on a Wednesday. There is no fixed time of day when the release will happen because that depends on the person who is finishing the release, it could therefore be Tuesday or Thursday depending on your timezone when its available for you. If there was no announcement made in the previous release notes or on another communication channel then the release will happen.
+
+Beta's are normally released on the 2nd Wednesday after the last major release. Please subscribe to the Beta Channel on the [Home Assistant Discord server](https://discord.gg/RMC8WkX) for help running beta versions.
+When a beta release is in progress the the release notes for it can be found here [Beta Release Notes](https://rc.home-assistant.io/latest-release-notes/).
+
+The release schedule is published in the upcoming events calender on the [Home Assistant Developers](https://developers.home-assistant.io/) website.
From b6ada31d4614041c7c70ecd44d28474fc19beca4 Mon Sep 17 00:00:00 2001
From: Dubh Ad
Date: Sat, 6 Jul 2019 09:42:25 +0100
Subject: [PATCH 05/44] Quick removal of links to setting the password (#9795)
API password is dead, we shouldn't be talking about it any more
---
source/_docs/ecosystem/certificates/lets_encrypt.markdown | 7 +------
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git a/source/_docs/ecosystem/certificates/lets_encrypt.markdown b/source/_docs/ecosystem/certificates/lets_encrypt.markdown
index 419a676890c..e9fbab0c19d 100644
--- a/source/_docs/ecosystem/certificates/lets_encrypt.markdown
+++ b/source/_docs/ecosystem/certificates/lets_encrypt.markdown
@@ -13,16 +13,11 @@ footer: true
If you are using Hass.io or Hassbian, do not use this guide. Instead, use the [DuckDNS add-on](/addons/duckdns/) for Hass.io or the [DuckDNS suite](https://github.com/home-assistant/hassbian-scripts/blob/master/docs/suites/duckdns.md) for Hassbian to automatically maintain a subdomain including HTTPS certificates via Let's Encrypt.
-
-Before exposing your Home Assistant instance to the outside world it is ESSENTIAL that you have set a password following the advice on the [http](/components/http/) page.
-
-
-
This guide was added by mf_social on 16/03/2017 and was valid at the time of writing. This guide makes the following assumptions:
* You can access your Home Assistant instance across your local network, and access the device that it is on via SSH from your local network.
* You know the internal IP address of your router and can access your router's configuration pages.
- * You have already set up a password for your Home Assistant instance, following the advice on this page: [http](/docs/configuration/basic/)
+ * You have already secured your Home Assistant instance, following the advice on [this page](/docs/configuration/securing/)
* You want to access your Home Assistant instance when you are away from home (ie, not connected to your local network) and secure it with a TLS/SSL certificate.
* You have a basic understanding of the phrases I have used so far.
* You are not currently running anything on port 80 on your network (you'd know if you were).
From 2069ab65a85da15b527808fe5f4c7af00baaf5f1 Mon Sep 17 00:00:00 2001
From: berightback-dev <52596688+berightback-dev@users.noreply.github.com>
Date: Sat, 6 Jul 2019 14:45:44 +0200
Subject: [PATCH 06/44] Update mosquitto.markdown (#9796)
In my case, user was not able to publish message with "topic #"
I had to add readwrite to it to work
I'm using Mosquitto 5.0
---
source/_addons/mosquitto.markdown | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/source/_addons/mosquitto.markdown b/source/_addons/mosquitto.markdown
index 06ff1adbc5c..24c4f3e2b8c 100644
--- a/source/_addons/mosquitto.markdown
+++ b/source/_addons/mosquitto.markdown
@@ -104,7 +104,7 @@ acl_file /share/mosquitto/accesscontrollist
3. Create `/share/mosquitto/accesscontrollist` with the contents:
```text
user [YOUR_MQTT_USER]
-topic #
+topic readwrite #
```
The `/share` folder can be accessed via SMB, or on the host filesystem under `/usr/share/hassio/share`.
From 6806bc199c7eed680dd8bdbc9a1abf0c5afa6882 Mon Sep 17 00:00:00 2001
From: aidbish <38182386+aidbish@users.noreply.github.com>
Date: Sun, 7 Jul 2019 03:22:02 +1000
Subject: [PATCH 07/44] Fix broken links (#9797)
* Fix broken link - pigpiod
relates to https://github.com/home-assistant/home-assistant.io/issues/9774
* Fix broken link - pencom
relates to https://github.com/home-assistant/home-assistant.io/issues/9774
* broken link - pencom
* fix broken link - radiothermostat
relates to https://github.com/home-assistant/home-assistant.io/issues/9774
* fix broken link - ruter
relates to https://github.com/home-assistant/home-assistant.io/issues/9774
* fix broken links - spc
relates to https://github.com/home-assistant/home-assistant.io/issues/9774
* fix broken link - sharp quatro
relates to https://github.com/home-assistant/home-assistant.io/issues/9774
---
source/_components/aquostv.markdown | 2 +-
source/_components/pencom.markdown | 2 +-
source/_components/radiotherm.markdown | 2 +-
source/_components/rpi_gpio_pwm.markdown | 2 +-
source/_components/ruter.markdown | 2 +-
source/_components/spc.markdown | 6 +++---
6 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/source/_components/aquostv.markdown b/source/_components/aquostv.markdown
index c69cfaefc23..16f4f1b6492 100644
--- a/source/_components/aquostv.markdown
+++ b/source/_components/aquostv.markdown
@@ -16,7 +16,7 @@ redirect_from:
- /components/media_player.aquostv/
---
-The `aquostv` platform allows you to control a [Sharp Aquos TV](http://www.sharp.ca/en-CA/ForHome/HomeEntertainment/LEDTV/QuattronPlus.aspx).
+The `aquostv` platform allows you to control a [Sharp Aquos TV](http://www.sharp-world.com/aquos/en/index.html).
When the TV is first connected, you will need to accept Home Assistant on the TV to allow communication.
diff --git a/source/_components/pencom.markdown b/source/_components/pencom.markdown
index 300fef6149b..b3ec93a6496 100644
--- a/source/_components/pencom.markdown
+++ b/source/_components/pencom.markdown
@@ -16,7 +16,7 @@ redirect_from:
- /components/switch.pencom/
---
-[Pencom Design](http://www.pencomdesign.com/) is a manufacturer of computer-controlled relay, I/O and custom boards for commercial and industrial applications. This interface to [Pencom's Relay Control Boards](https://www.pencomdesign.com/relay-boards/) is designed to work over an ethernet to serial adapter (NPort). Each switch (relay) can be turned on/off, and the state of the relay can be read.
+[Pencom Design](https://www.pencomdesign.com/) is a manufacturer of computer-controlled relay, I/O and custom boards for commercial and industrial applications. This interface to [Pencom's Relay Control Boards](https://www.pencomdesign.com/relay-boards) is designed to work over an ethernet to serial adapter (NPort). Each switch (relay) can be turned on/off, and the state of the relay can be read.
## Configuration
diff --git a/source/_components/radiotherm.markdown b/source/_components/radiotherm.markdown
index 2bf1be5021a..a83284d1274 100644
--- a/source/_components/radiotherm.markdown
+++ b/source/_components/radiotherm.markdown
@@ -17,7 +17,7 @@ redirect_from:
---
-The `radiotherm` climate platform let you control a thermostat from [Radio Thermostat](http://www.radiothermostat.com/) or [3M Filtrete](http://www.radiothermostat.com/filtrete/products/). Your thermostat must have the Wi-Fi module installed and connected to your network.
+The `radiotherm` climate platform let you control a thermostat from [Radio Thermostat](http://www.radiothermostat.com/) or [3M Filtrete](https://my.radiothermostat.com/filtrete/). Your thermostat must have the Wi-Fi module installed and connected to your network.
The underlying library supports:
diff --git a/source/_components/rpi_gpio_pwm.markdown b/source/_components/rpi_gpio_pwm.markdown
index 803c6c02e0a..89a7f56ec56 100644
--- a/source/_components/rpi_gpio_pwm.markdown
+++ b/source/_components/rpi_gpio_pwm.markdown
@@ -18,7 +18,7 @@ redirect_from:
The `rpi_gpio_pwm` platform allows to control multiple lights using pulse-width modulation, for example led strips. It supports one-color, RGB and RGBW LEDs driven by GPIOs of a Raspberry Pi or a PCA9685 controller.
-For controlling the GPIOs, the platform connects to the [pigpio-daemon](http://abyz.co.uk/rpi/pigpio/pigpiod.html), which must be running. On Raspbian Jessie 2016-05-10 or newer the `pigpio` library is already included. On other operating systems it needs to be installed first (see [installation instructions](https://github.com/soldag/python-pwmled#installation)).
+For controlling the GPIOs, the platform connects to the [pigpio-daemon](http://abyz.me.uk/rpi/pigpio/pigpiod.html), which must be running. On Raspbian Jessie 2016-05-10 or newer the `pigpio` library is already included. On other operating systems it needs to be installed first (see [installation instructions](https://github.com/soldag/python-pwmled#installation)).
## Configuration
diff --git a/source/_components/ruter.markdown b/source/_components/ruter.markdown
index c43758a4c90..7bc7e8a4a81 100644
--- a/source/_components/ruter.markdown
+++ b/source/_components/ruter.markdown
@@ -58,5 +58,5 @@ name:
default: Ruter
{% endconfiguration %}
-[ruter]: https://ruter.no/reiseplanlegger/Stoppested
+[ruter]: https://ruter.no/reiseplanlegger/
[ruter-api]: http://reisapi.ruter.no/Help
diff --git a/source/_components/spc.markdown b/source/_components/spc.markdown
index e2d257b622d..176cfe18866 100644
--- a/source/_components/spc.markdown
+++ b/source/_components/spc.markdown
@@ -19,7 +19,7 @@ redirect_from:
- /components/alarm_control_panel.spc/
---
-Home Assistant has support to integrate your [Vanderbilt SPC](http://www.spc-intruder-detection.com/ssp-spc/) alarm panel and any connected motion, door and smoke sensors.
+Home Assistant has support to integrate your [Vanderbilt SPC](https://www.spcsupportinfo.com/SPCConnectPro/) alarm panel and any connected motion, door and smoke sensors.
Integration with SPC is done through a third-party API gateway called [SPC Web Gateway](http://www.lundix.se/smarta-losningar/) which must be installed and configured somewhere on your network.
@@ -52,7 +52,7 @@ Supported sensors will be automatically discovered and added, however they will
## Alarm
-The `spc` alarm control panel platform allows you to control your [Vanderbilt SPC](https://www.spcsupportinfo.com/) alarms.
+The `spc` alarm control panel platform allows you to control your [Vanderbilt SPC](https://www.spcsupportinfo.com/SPCConnectPro/) alarms.
The `changed_by` attribute enables one to be able to take different actions depending on who armed/disarmed the alarm in [automation](/getting-started/automation/).
@@ -73,6 +73,6 @@ automation:
## Binary Sensor
-The `spc` platform allows you to get data from your [Vanderbilt SPC](http://www.spc-intruder-detection.com/ssp-spc/) binary sensors from within Home Assistant.
+The `spc` platform allows you to get data from your [Vanderbilt SPC](https://www.spcsupportinfo.com/SPCConnectPro/) binary sensors from within Home Assistant.
Check the [type/class](/components/binary_sensor/) list for a possible visualization of your zone. Currently motion, smoke and door sensors are supported.
From ec90c29421c47f483dadfd77c16333f81b641f47 Mon Sep 17 00:00:00 2001
From: Mark LUCAS
Date: Sun, 7 Jul 2019 21:37:34 +0200
Subject: [PATCH 08/44] Add new supported models (#9800)
---
source/_components/samsungtv.markdown | 1 +
1 file changed, 1 insertion(+)
diff --git a/source/_components/samsungtv.markdown b/source/_components/samsungtv.markdown
index 7b816363e0b..22e518a0812 100644
--- a/source/_components/samsungtv.markdown
+++ b/source/_components/samsungtv.markdown
@@ -78,6 +78,7 @@ Currently known supported models:
- F6400
- F6400AF
- F6500
+- F7000
- F8000BF
- K5579 (port must be set to 8001, On/Off, Forward/Backward, Volume control, but no Play button)
- K5600AK (partially supported, turn on works but state is not updated)
From b241c227d045483e047b990518fecfc955be33dc Mon Sep 17 00:00:00 2001
From: Chris Johnston
Date: Sun, 7 Jul 2019 13:59:58 -0700
Subject: [PATCH 09/44] Fix formatting of installation commands (#9803)
* Fix formatting of installation commands
This change fixes the formatting of the generic linux host
installation commands so that they all begin with `$`.
This ensures that they are rendered correctly in the documentation.
Previously, the commands under `$ sudo -i` all began with `#` (to
indicate that the shell was running as root). While this is correct,
the markdown formatting thinks that they are comments, so they
are rendered in a light gray color.
* remove line start symbol from commads
none of the commands produce any output, so all of the symbols
should be removed
---
source/hassio/installation.markdown | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/source/hassio/installation.markdown b/source/hassio/installation.markdown
index 06c0d5ecea3..0209bf77854 100644
--- a/source/hassio/installation.markdown
+++ b/source/hassio/installation.markdown
@@ -82,7 +82,7 @@ Best practice for updating a Hass.io installation:
SSH to your Hass.io system, or connect to the console, and run:
-```
+```bash
hassio ha update --version=0.XX.X
```
@@ -140,18 +140,18 @@ You also need to have Docker-CE installed. There are well-documented procedures
To perform the Hass.io installation on Ubuntu, run the following commands:
```bash
-$ sudo -i
-# apt-get install software-properties-common
-# add-apt-repository universe
-# apt-get update
-# apt-get install -y apparmor-utils apt-transport-https avahi-daemon ca-certificates curl dbus jq network-manager socat
-# curl -fsSL get.docker.com | sh
+sudo -i
+apt-get install software-properties-common
+add-apt-repository universe
+apt-get update
+apt-get install -y apparmor-utils apt-transport-https avahi-daemon ca-certificates curl dbus jq network-manager socat
+curl -fsSL get.docker.com | sh
```
And to install Hass.io the one below. That one is used also for other distributions.
```bash
-# curl -sL "https://raw.githubusercontent.com/home-assistant/hassio-installer/master/hassio_install.sh" | bash -s
+curl -sL "https://raw.githubusercontent.com/home-assistant/hassio-installer/master/hassio_install.sh" | bash -s
```
From e805ffc0d5c26a0db3c1d0bcb29899d79a048286 Mon Sep 17 00:00:00 2001
From: Klaas Schoute
Date: Mon, 8 Jul 2019 12:24:54 +0200
Subject: [PATCH 10/44] =?UTF-8?q?=F0=9F=94=A8=20Fix=20broken=20links=20(pa?=
=?UTF-8?q?rt=201)=20(#9805)?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
* :hammer: Fix broken links (part 1)
* :ambulance: Recover the new usernames
---
source/_posts/2015-05-14-release-notes.markdown | 4 ++--
source/_posts/2015-06-10-release-notes.markdown | 2 +-
...aspberry-pi-squeezebox-asuswrt-support.markdown | 4 ++--
...-revamped-ui-and-improved-distribution.markdown | 2 +-
...26-firetv-and-radiotherm-now-supported.markdown | 4 ++--
...rs-binary-sensors-and-influxdb-support.markdown | 6 ++----
...12-20-amazon-echo-icloud-and-templates.markdown | 5 ++---
...-17-extended-support-for-diy-solutions.markdown | 2 +-
...-01-29-insteon-lifx-twitter-and-zigbee.markdown | 5 ++---
...embedded-mqtt-broker-uber-yamaha-growl.markdown | 3 +--
source/_posts/2016-05-21-release-020.markdown | 3 +--
...6-07-16-sqlalchemy-knx-join-simplisafe.markdown | 2 +-
...end-panels--jupyter-notebooks--directv.markdown | 5 ++---
...-08-13-foursquare-fast-com-ffmpeg-gpsd.markdown | 3 +--
...-27-notifications-hue-fake-unification.markdown | 1 -
...016-09-29-async-sleepiq-emoncms-stocks.markdown | 3 +--
...6-11-05-hacktoberfest-influxdb-weather.markdown | 5 ++---
.../2017-01-14-iss-usps-images-packages.markdown | 2 +-
source/_posts/2017-01-28-face-coffee-wink.markdown | 5 ++---
...2017-02-11-alert-appletv-mqtt-yeelight.markdown | 5 ++---
...-25-config-panel-and-state-restoration.markdown | 2 +-
...purpose-any-android-phone-as-ip-camera.markdown | 14 ++++++--------
.../2017-03-25-todo-volumio-workday.markdown | 2 +-
.../2017-04-22-ikea-tradfri--spotify.markdown | 3 +--
source/_posts/2017-07-02-release-48.markdown | 8 ++++----
source/_posts/2017-08-26-release-0-52.markdown | 8 ++++----
26 files changed, 46 insertions(+), 62 deletions(-)
diff --git a/source/_posts/2015-05-14-release-notes.markdown b/source/_posts/2015-05-14-release-notes.markdown
index 1b16ae2fa74..946a8d5b055 100644
--- a/source/_posts/2015-05-14-release-notes.markdown
+++ b/source/_posts/2015-05-14-release-notes.markdown
@@ -69,13 +69,13 @@ sensor:
```
__InstaPush__
- [Fabaff](https://github.com/fabaff) has contributed support for [InstaPush](https://instapush.im). This will allow you send messages from Home Assistant to your iOS and Android devices.
+[Fabaff](https://github.com/fabaff) has contributed support for InstaPush. This will allow you send messages from Home Assistant to your iOS and Android devices.
```yaml
# Example configuration.yaml entry
notify:
platform: instapush
- # Get those by creating a new application, event, and tracker on https://instapush.im
+ # Get those by creating a new application, event and tracker
api_key: ABCDEFGHJKLMNOPQRSTUVXYZ
app_secret: ABCDEFGHJKLMNOPQRSTUVXYZ
event: ABCDEFGHJKLMNOPQRSTUVXYZ
diff --git a/source/_posts/2015-06-10-release-notes.markdown b/source/_posts/2015-06-10-release-notes.markdown
index 551a199f485..187770a673a 100644
--- a/source/_posts/2015-06-10-release-notes.markdown
+++ b/source/_posts/2015-06-10-release-notes.markdown
@@ -12,7 +12,7 @@ categories: Release-Notes
Wow, almost a month has gone by since the last release and this release is *packed*. The biggest part of this release is probably one that you won't notice: the frontend has been upgraded from Polymer 0.5 to the brand new released Polymer 1.0. Polymer has been declared stable by the Google overlords which will allow us to expand functionality that was waiting for this moment to arrive.
-This release sets a record for the amount of people involved: 8! [Andythigpen](https://github.com/Andythigpen), [Jamespcole](https://github.com/Jamespcole), [Azelphur](https://github.com/Azelphur), [Fabaff](https://github.com/Fabaff), [Dutchy-](https://github.com/Dutchy-), [Fbradyirl](https://github.com/Fbradyirl), [wind-rider](https://github.com/wind-rider) and [ettisan](https://github.com/ettisan), thanks a lot for your contributions!
+This release sets a record for the amount of people involved: 8! [Andythigpen](https://github.com/Andythigpen), [Jamespcole](https://github.com/Jamespcole), [Azelphur](https://github.com/Azelphur), [Fabaff](https://github.com/Fabaff), [Dutchy-](https://github.com/Dutchy-), [Fbradyirl](https://github.com/Fbradyirl), wind-rider and [ettisan](https://github.com/ettisan), thanks a lot for your contributions!
A big improvement has been brought this release by wind-rider. He took the time to revive the Chromecast support and started improving the media player integration. This triggered other people to join in resulting in a revamped media player experience and support for the Music Player Daemon.
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 2707b3e7f0f..4cb699c9bb1 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
@@ -13,9 +13,9 @@ categories: Release-Notes
It's time for the August release and there is some serious good stuff this time. The core of Home Assistant has gone some serious clean up and a bump in test coverage thanks to [@balloob](https://github.com/balloob). If you're a developer, make sure you read up on [the deprecation notices](https://github.com/home-assistant/home-assistant/pull/251). [@fabaff](https://github.com/fabaff) did another great round of documenting all the various components.
__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].
+ 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 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/home-assistant/home-assistant/blob/dev/config/custom_components/mqtt_example.py
[mqtt-automation]: /getting-started/automation-trigger/#mqtt-trigger
[mqtt-component]: /components/mqtt/
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 e690fbf3136..daf238a786f 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
@@ -91,7 +91,7 @@ device_tracker:
```
__DHT temperature and humidity sensors__
-[@MakeMeASandwich](https://github.com/makemeasandwich) has contributed support for DHT temperature and humidity sensors. It allows you to get the current temperature and humidity from a DHT11, DHT22, or AM2302 device.
+@MakeMeASandwich has contributed support for DHT temperature and humidity sensors. It allows you to get the current temperature and humidity from a DHT11, DHT22, or AM2302 device.
```yaml
# Example configuration.yaml entry
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 5fef5d532a5..5108b72bed9 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
@@ -20,10 +20,10 @@ After two weeks of hard work I'm proud to announce the release of Home Assistant
- 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.locative/) now supported ([@wind-rider](https://github.com/wind-rider))
+ - Device Tracker: [Geofancy](/components/device_tracker.locative/) now supported (@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))
+ - Light: [Hyperion](/components/light.hyperion/) now supported (@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))
diff --git a/source/_posts/2015-12-06-locks-rollershutters-binary-sensors-and-influxdb-support.markdown b/source/_posts/2015-12-06-locks-rollershutters-binary-sensors-and-influxdb-support.markdown
index 14e1b5685e4..a01a119c0ac 100644
--- a/source/_posts/2015-12-06-locks-rollershutters-binary-sensors-and-influxdb-support.markdown
+++ b/source/_posts/2015-12-06-locks-rollershutters-binary-sensors-and-influxdb-support.markdown
@@ -17,7 +17,7 @@ It's been a few weeks but we managed to polish a nice new release of Home Assist
- New [lock component] including [Wink][lock.wink] support ([@miniconfig])
- New [binary sensor component] including [aRest][binary_sensor.arest] and [MQTT][binary_sensor.mqtt] support ([@fabaff])
- - New [rollershutter component] including [MQTT][rollershutter.mqtt] support ([@sfam])
+ - New rollershutter component including MQTT support ([@sfam])
- New [InfluxDB component] to store data in InfluxDB ([@fabaff])
- Thermostat: [Ecobee] now supported ([@nkgilley])
- Thermostat: [Homematic] now supported ([@goir])
@@ -31,10 +31,8 @@ To update, run `pip3 install --upgrade homeassistant`.
[binary sensor component]: /components/binary_sensor/
[binary_sensor.arest]: /components/binary_sensor.arest/
[binary_sensor.mqtt]: /components/binary_sensor.mqtt/
-[rollershutter component]: /components/rollershutter/
-[rollershutter.mqtt]: /components/rollershutter.mqtt/
[InfluxDB component]: /components/influxdb/
-[Ecobee]: /components/thermostat.ecobee/
+[Ecobee]: /components/ecobee/#thermostat
[Homematic]: /components/thermostat.homematic/
[parsing JSON values]: /components/mqtt/#processing-json
diff --git a/source/_posts/2015-12-20-amazon-echo-icloud-and-templates.markdown b/source/_posts/2015-12-20-amazon-echo-icloud-and-templates.markdown
index fe534bc2edd..035c87c4e37 100644
--- a/source/_posts/2015-12-20-amazon-echo-icloud-and-templates.markdown
+++ b/source/_posts/2015-12-20-amazon-echo-icloud-and-templates.markdown
@@ -35,7 +35,7 @@ Alrighty, it's time for Home Assistant 0.10. A lot amazing things have changed a
[iCloud]: /components/device_tracker.icloud/
[Twitch]: /components/sensor.twitch/
[Template]: /topics/templating/
-[Heatmiser]: /components/thermostat.heatmiser/
+[Heatmiser]: /components/heatmiser/
[Dweet.io]: /components/sensor.dweet/
[Alexa/Amazon echo]: /components/alexa/
[FritzBox]: /components/device_tracker.fritz/
@@ -78,7 +78,7 @@ Affected components and platforms:
- sensor: [rest][sensor.rest]
- sensor: [MQTT][sensor.mqtt]
- switch: [MQTT][switch.mqtt]
- - rollershutter: [MQTT][rollershutter.mqtt]
+ - rollershutter: MQTT
- light: [MQTT][light.mqtt]
- binary_sensor: [MQTT][binary_sensor.mqtt]
- automation: [numeric_state][automation-numeric-state]
@@ -88,7 +88,6 @@ Affected components and platforms:
[sensor.rest]: /components/sensor.rest/
[sensor.mqtt]: /components/sensor.mqtt/
[switch.mqtt]: /components/switch.mqtt/
-[rollershutter.mqtt]: /components/rollershutter.mqtt/
[light.mqtt]: /components/light.mqtt/
[binary_sensor.mqtt]: /components/binary_sensor.mqtt/
[automation-numeric-state]: /getting-started/automation-trigger/#numeric-state-trigger
diff --git a/source/_posts/2016-01-17-extended-support-for-diy-solutions.markdown b/source/_posts/2016-01-17-extended-support-for-diy-solutions.markdown
index 9c2cba7e3f9..9b6e1dab755 100644
--- a/source/_posts/2016-01-17-extended-support-for-diy-solutions.markdown
+++ b/source/_posts/2016-01-17-extended-support-for-diy-solutions.markdown
@@ -15,7 +15,7 @@ First release of 2016 and we are on 🔥! The [main repository][github-ha] has p
[github-ha]: https://github.com/home-assistant/home-assistant/
[release-pr]: https://github.com/home-assistant/home-assistant/pull/883#partial-users-participants
-
+
- [MySensors] revamped and switch support added ([@MartinHjelmare][@MartinHjelmare])
- Full refactor of RPi GPIO. Now includes [binary sensor][rpi-bs] and [switch][rpi-s] ([@sfam])
diff --git a/source/_posts/2016-01-29-insteon-lifx-twitter-and-zigbee.markdown b/source/_posts/2016-01-29-insteon-lifx-twitter-and-zigbee.markdown
index 11c46a5ff55..ed5e34e7532 100644
--- a/source/_posts/2016-01-29-insteon-lifx-twitter-and-zigbee.markdown
+++ b/source/_posts/2016-01-29-insteon-lifx-twitter-and-zigbee.markdown
@@ -22,7 +22,7 @@ This release includes a very frequent requested feature: the ability to organize
Example of the new views in the frontend. Learn more.