Merge branch 'current' into rc

source/_components/aftership.markdown

@@ -60,7 +60,7 @@ api_key:
 | `slug` | `False` | string | Carrier e.g. `fedex`
 | `title` | `False` | string | Friendly name of package
 
- ## {% linkable_title Service `remove_tracking` %}
+## {% linkable_title Service `remove_tracking` %}
 
  You can use the service `aftership.remove_tracking` to remove trackings from Aftership.
 

source/_components/darksky.markdown

@@ -159,6 +159,10 @@ scan_interval:
   type: time
 {% endconfiguration %}
 
+<p class='note'>
+Please note that some monitored conditions, such as `temperature_high` or `temperature_low`, may only work when setting the `forecast` attribute to at least `0` (current day).
+</p>
+
 #### {% linkable_title Time period dictionary example %}
 
 ```yaml

source/_components/emulated_hue.markdown

@@ -16,7 +16,7 @@ ha_qa_scale: internal
 ---
 
 <p class='note warning'>
-Be aware that `emulated_hue` doesn't work for new **Google Home** users. If you're a new user of Google Home, use the [Google Assistant component](/components/google_assistant/).
+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.
 </p>
 
 The `emulated_hue` component provides a virtual Philips Hue bridge, written entirely in software, which allows services that work with the Hue API to interact with Home Assistant

source/_components/flux_led.markdown

@@ -21,14 +21,14 @@ The `flux_led` support is integrated into Home Assistant as a light platform. Se
 Example of bulbs:
 
 - [Flux Smart Lighting](http://www.fluxsmartlighting.com/)
-- [MagicLight® Plus - WiFi Smart LED Light Bulb4](https://www.amazon.com/gp/product/B00NOC93NG)
+- [MagicLight® Plus - WiFi Smart LED Light Bulb4](https://amzn.to/2X0Zath)
-- [Flux WiFi Smart LED Light Bulb4](http://smile.amazon.com/Flux-WiFi-Smart-Light-Bulb/dp/B01A6GHHTE)
+- [Flux WiFi Smart LED Light Bulb4](https://amzn.to/2X0dVwu)
-- [WIFI smart LED light Bulb1](http://smile.amazon.com/gp/product/B01CS1EZYK)
+- [WIFI smart LED light Bulb1](https://amzn.to/2J2fksr)
 
 Examples of controllers:
 
-- [Ledenet WiFi RGBW Controller](https://www.amazon.com/gp/product/B01DY56N8U)
+- [Ledenet WiFi RGBW Controller](https://amzn.to/2WZKXNa)
-- [SUPERNIGHT WiFi Wireless LED Smart Controller](https://www.amazon.com/dp/B01JZ2SI6Q)
+- [SUPERNIGHT WiFi Wireless LED Smart Controller](https://amzn.to/2WURx7w)
 
 
 ### {% linkable_title Configuration Details %}

source/_components/hook.markdown

@@ -17,7 +17,7 @@ redirect_from:
 
 The `hook` component allows you to control the [Hook Smart Home Hub](http://www.hooksmarthome.com/) from within Home Assistant.
 
-Hook allows you to control cheap mains electrical outlets, like these ones at [Amazon](https://www.amazon.com/Etekcity-Wireless-Electrical-Household-Appliances/dp/B00DQELHBS).
+Hook allows you to control cheap mains electrical outlets, like these ones at [Amazon](https://amzn.to/2WVZdGG).
 
 In short, Hook is an RF to Wi-Fi bridge, controlling devices that receive commands at 315MHz and 433MHz. Unfortunately, this does not allow Hook to determine if the command was successful, so the state is assumed.
 

source/_components/recorder.markdown

@@ -196,7 +196,7 @@ homeassistant@homeassistant:~$ source /srv/homeassistant/bin/activate
 (homeassistant) homeassistant@homeassistant:~$ pip3 install mysqlclient
 ```
 
-For MariaDB you may have to install a few dependencies. If you're using MariaDB version 10.2, `libmariadbclient-dev` was renamed to `libmariadb-dev`; please install the correct package based on your MariaDB version.
+For MariaDB you may have to install a few dependencies. If you're using MariaDB version 10.2, `libmariadbclient-dev` was renamed to `libmariadb-dev`. If you're using MariaDB 10.3, the package `libmariadb-dev-compat` must also be installed. Please install the correct packages based on your MariaDB version.
 
 On the Python side we use the `mysqlclient`:
 

source/_components/samsungtv.markdown

@@ -70,6 +70,7 @@ Currently known supported models:
 - EH5300
 - EH5600
 - ES5500
+- ES5700
 - ES6300
 - ES6800
 - F4580

source/_docs/ecosystem/hass-configurator.markdown

@@ -37,7 +37,7 @@ Screenshot of the HASS Configurator.
 This tool allows you to browse your filesystem and modify files. So be careful which files you edit, or you might break critical parts of your system.<br />
 Consider running the configurator as a user with limited privileges to limit possible damage.</p>
 
-### {% linkable_title Installation (Linux, OS X) %}
+### {% linkable_title Installation (Linux, macOS) %}
 There are no dependencies on Python modules that are not part of the standard library. And all the fancy JavaScript libraries are loaded from CDN (which means this doesn't work when you're offline).
 - Copy [configurator.py](https://github.com/danielperna84/hass-configurator/blob/master/configurator.py) to your Home Assistant configuration directory (e.g `/home/homeassistant/.homeassistant`): `wget https://raw.githubusercontent.com/danielperna84/hass-configurator/master/configurator.py`
 - Make it executable: `sudo chmod 755 configurator.py`

source/_docs/installation/macos.markdown

@@ -11,12 +11,14 @@ footer: true
 
 [macOS](http://www.apple.com/macos/) is available by default on Apple computer. If you run a different operating system, please refer to the other section of the documentation.
 
-To run Home Assistant on macOS you need to install Python first. Download Python 3.5.3 or later from [https://www.python.org/downloads/mac-osx/](https://www.python.org/downloads/mac-osx/) and follow the instructions of the installer.
+To run Home Assistant on macOS, you need to install Python first. Download Python 3.6 or later (at this time, we recommend Python 3.7) from [https://www.python.org/downloads/mac-osx/](https://www.python.org/downloads/mac-osx/) and follow the instructions of the installer.
 
-Open a terminal and install Home Assistant.
+Open a terminal and install Home Assistant in a virtual environment:
 
 ```bash
+$ python3 -m venv homeassistant
+$ source homeassistant/bin/activate
 $ pip3 install homeassistant
 ```
 
-Check this [video](https://www.youtube.com/watch?v=hej6ipN86ls) for the installation on macOS.
+You can then configure Home Assistant to autostart by following [this guide](/docs/autostart/macos/).

source/_docs/z-wave/installation.markdown

@@ -232,6 +232,18 @@ $ ls /dev/cu.usbmodem*
 
 If your device path changes when you restart, see [this guide](http://hintshop.ludvig.co.nz/show/persistent-names-usb-serial-devices/) on fixing it.
 
+## {% linkable_title Ubuntu and Debian based host system %}
+
+If your instance is running on a Debian based system, e.g., Ubuntu, the ModemManager may cause unexpected issues.
+
+The ModemManager might be claiming or interfering with a USB Z-Wave stick, like the much used Aeotec ones. If you experience issues where the stick stops responding, needs to be re-plugged or Home Assistant needs a restart to get Z-Wave back, chances are high that the ModemManager is causing the issue.
+
+ Execute the following command on your host system to disable the ModemManager:
+
+ ```bash
+systemctl disable ModemManager.service
+```
+
 ### {% linkable_title Component could not be set up %}
 
 Sometimes the device may not be accessible and you'll get an error message upon startup about not being able to set up Z-Wave. Run the following command for your device path (here we're using `/dev/ttyAMA0` for our Razberry board):

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

@@ -47,8 +47,8 @@ Next I wrote [scripts](/components/script/) that are run whenever the washer or
 Materials used:
 
  - [Moteino](https://lowpowerlab.com/moteino/)
- - [2 x Accelerometers](http://www.amazon.com/gp/product/B008BOPN40)
+ - [2 x Accelerometers](https://amzn.to/2WXa2s5)
- - [2 x Reed switch](http://www.amazon.com/gp/product/B004PARDRO)
+ - [2 x Reed switch](https://amzn.to/2X0ZuZ2)
  - [Home Assistant](/)
 
 [Sketch for the Moteino is available here.](https://codebender.cc/sketch:144743)
@@ -144,4 +144,3 @@ Resources used:
 
  - [Inspiration and Help with Arduino code](http://www.instructables.com/id/Uber-Home-Automation-w-Arduino-Pi/step13/Washer-Dryer-Smartifier-Water-Leak-Sensor/)
  - [Moteino Code](https://github.com/LowPowerLab/RFM69/)
-

source/_posts/2016-08-03-laundry-automation-update.markdown

@@ -48,9 +48,9 @@ Next I wrote [scripts](/components/script/) that are run whenever the washer or
 
 Materials used:
 
- - [NodeMCU](https://www.amazon.com/gp/product/B010O1G1ES)
+ - [NodeMCU](https://amzn.to/2Y9Mmxk)
- - [2 x Accelerometers](http://www.amazon.com/gp/product/B008BOPN40)
+ - [2 x Accelerometers](https://amzn.to/2WXa2s5)
- - [2 x Reed switch](http://www.amazon.com/gp/product/B004PARDRO)
+ - [2 x Reed switch](https://amzn.to/2X0ZuZ2)
 
 [Sketch for the NodeMCU is available here.](https://github.com/nkgilley/nodemcu-laundry/blob/master/nodemcu-laundry.ino)
 
@@ -112,4 +112,3 @@ script:
 Resources used:
 
  - [Inspiration and Help with Arduino code](http://www.instructables.com/id/Uber-Home-Automation-w-Arduino-Pi/step13/Washer-Dryer-Smartifier-Water-Leak-Sensor/)
-

source/_posts/2019-06-05-release-94.markdown

@@ -161,6 +161,22 @@ Because of this, we changed how packages are installed when running Home Assista
 [owntracks docs]: /components/owntracks/
 [watson_tts docs]: /components/watson_tts/
 
+## {% linkable_title Release 0.94.4 - June 19 %}
+
+- Fixing tplink issues with offline devices during setup ([@vangorra] - [#23668]) ([tplink docs])
+- Fix zeroconf migration messing up ESPHome discovery ([@OttoWinter] - [#24578]) ([esphome docs])
+- Fixed issue #24335 ([@Swamp-Ig] - [#24612]) ([sun docs])
+
+[#23668]: https://github.com/home-assistant/home-assistant/pull/23668
+[#24578]: https://github.com/home-assistant/home-assistant/pull/24578
+[#24612]: https://github.com/home-assistant/home-assistant/pull/24612
+[@OttoWinter]: https://github.com/OttoWinter
+[@Swamp-Ig]: https://github.com/Swamp-Ig
+[@vangorra]: https://github.com/vangorra
+[esphome docs]: /components/esphome/
+[sun docs]: /components/sun/
+[tplink docs]: /components/tplink/
+
 ## {% linkable_title If you need help... %}
 
 ...don't hesitate to use our very active [forums](https://community.home-assistant.io/) or join us for a little [chat](https://discord.gg/c5DvZ4e). The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks.

source/getting-started/automation.markdown

@@ -34,7 +34,7 @@ In the trigger section, click on the dropdown and change trigger type to "Sun".
 A new automation with a sun trigger filled in.
 </p>
 
-Once we have defined our trigger, scroll down to the action section. Make sure trigger type is set to "Call Service" and change the service to `light.turn_on`. For this automation we're going to turn on all lights, so let's change the service data to `{ "entity_id": "all" }`.
+Once we have defined our trigger, scroll down to the action section. Make sure the action type is set to "Call Service" and change the service to `light.turn_on`. For this automation we're going to turn on all lights, so let's change the service data to `{ "entity_id": "all" }`.
 
 <p class='img'>
 <img src='/images/getting-started/automation-new-action.png'>

source/getting-started/index.markdown

@@ -41,9 +41,9 @@ Follow this guide if you want to get started with Home Assistant easily, or if y
 
 We will need a few things to get started with installing Home Assistant. The latest Raspberry Pi model makes a good and affordable starting point for your home automation journey. Links below are linking to Amazon US. If you're not in the US, you should be able to find these items in web stores in your country.
 
-- [Raspberry Pi 3 Model B+](http://a.co/ak2SQor) + [Power Supply](https://www.raspberrypi.org/help/faqs/#powerReqs) (at least 2.5A)
+- [Raspberry Pi 3 Model B+](https://amzn.to/2IAyNl0) + [Power Supply](https://www.raspberrypi.org/help/faqs/#powerReqs) (at least 2.5A)
-- [Micro SD Card](http://a.co/gslOydD). Get one that is Class 10 as they are more reliable. Size 32 GB or bigger recommended.
+- [Micro SD Card](https://amzn.to/2X0Z2di). Ideally get one that is [Application Class 2](https://www.sdcard.org/developers/overview/application/index.html) as they handle small I/O much more consistently than cards not optimized to host applications. Size 32 GB or bigger recommended.
-- SD Card reader. Part of most laptops, and also available as [standalone USB sticks](http://a.co/5FCyb0N) (the brand doesn't matter, just pick the cheapest)
+- SD Card reader. Part of most laptops, and also available as [standalone USB sticks](https://amzn.to/2WWxntY) (the brand doesn't matter, just pick the cheapest)
 - Ethernet cable (optional, Hass.io can work with WiFi as well)
 
 ### {% linkable_title Software requirements %}

source/hassio/zwave.markdown

@@ -16,7 +16,7 @@ zwave:
   usb_path: /dev/ttyACM0
 ```
 
-### {% linkable_title RAZBERRY BOARD %}
+## {% linkable_title RAZBERRY BOARD %}
 
 If you need GPIO on Raspberry Pi 3 for your Z-Wave module, add the following line into `config.txt` (you have to access that on the SD card directly. Simply plug it into your PC and edit it there. The `config.txt` is not accessible from your Hass.io system, you may need to open the SD card on a Windows or Linux system.):
 
@@ -31,7 +31,7 @@ zwave:
   usb_path: /dev/ttyAMA0
 ```
 
-### {% linkable_title HUSBZB-1 %}
+## {% linkable_title HUSBZB-1 %}
 
 ```yaml
 zwave:
@@ -42,6 +42,18 @@ zha:
   database_path: /config/zigbee.db
 ```
 
+## {% linkable_title Ubuntu and Debian based host system %}
+
+If your instance is running on a Debian based system, e.g., Ubuntu, the ModemManager may cause unexpected issues.
+
+The ModemManager might be claiming or interfering with a USB Z-Wave stick, like the much used Aeotec ones. If you experience issues where the stick stops responding, needs to be re-plugged or Home Assistant needs a restart to get Z-Wave back, chances are high that the ModemManager is causing the issue.
+
+Execute the following command on your host system to disable the ModemManager:
+
+```bash
+systemctl disable ModemManager.service
+```
+
 ### {% linkable_title Finding the path %}
 
 If the above defaults don't work, you can check what hardware has been found using the [`hassio` command](/hassio/commandline/#hardware):