Merge remote-tracking branch 'origin/current' into rc

source/_addons/mosquitto.markdown

@@ -23,7 +23,7 @@ Set up [Mosquitto](https://mosquitto.org/) as MQTT broker.
 
 <div class='warning note'>
 
-Since version 4.1 of the addon, an explicit ACL definition is now required, [see these instructions](https://www.home-assistant.io/addons/mosquitto/#access-control-lists-acls).
+Since version 4.1 of the addon, an explicit ACL definition is now required if you plan to use legacy logins and `"anonymous": true` [see these instructions](https://www.home-assistant.io/addons/mosquitto/#access-control-lists-acls).
 
 </div>
 

source/_components/androidtv.markdown

@@ -174,7 +174,7 @@ If you get a "Device authentication required, no keys available" error when tryi
 In the dialog appearing on your Android TV / Fire TV, you must check the box that says "always allow connections from this device." ADB authentication in Home Assistant will only work using a trusted key.
 </div>
 
-Once you've successfully connected to your Android TV / Fire TV via the command `adb connect <ipaddress>`, the file `adbkey` will be created on your computer. The default locations for this file is (from [https://developer.android.com/studio/command-line/adb](https://developer.android.com/studio/command-line/adb)):
+Once you've successfully connected to your Android TV / Fire TV via the command `adb connect <ipaddress>:5555`, the file `adbkey` will be created on your computer. The default locations for this file is (from [https://developer.android.com/studio/command-line/adb](https://developer.android.com/studio/command-line/adb)):
 
 - Linux and Mac: `$HOME/.android.`
 - Windows: `%userprofile%\.android.`

source/_components/bluetooth_le_tracker.markdown

@@ -37,7 +37,7 @@ device_tracker:
 track_new_devices:
   description: If new discovered devices are tracked by default.
   required: false
-  default: true
+  default: false
   type: boolean
 interval_seconds:
   description: Seconds between each scan for new devices.

source/_components/onkyo.markdown

@@ -10,8 +10,8 @@ redirect_from:
  - /components/media_player.onkyo/
 ---
 
-
+The `onkyo` platform allows you to control a [Onkyo](http://www.onkyo.com/), [Integra](http://www.integrahometheater.com/)
-The `onkyo` platform allows you to control a [Onkyo](http://www.onkyo.com/) and some recent [Pioneer](http://www.pioneerelectronics.com) receivers from Home Assistant. Please be aware that you need to enable "Network Standby" for this integration to work in your Hardware.
+ and some recent [Pioneer](http://www.pioneerelectronics.com) receivers from Home Assistant. Please be aware that you need to enable "Network Standby" for this integration to work in your Hardware.
 
 ## Configuration
 

source/_components/template.markdown

@@ -88,7 +88,7 @@ sensor:
 
 ### Startup
 
-If you are using the state of a platform that takes extra time to load, the Template Sensor may get an `unknown` state during startup. To avoid this (and the resulting error messages in your log file), you can use `is_state()` function in your template. For example, you would replace {% raw %}`{{ is_state('switch.source', 'on') }}`{% endraw %} with this equivalent that returns `true`/`false` and never gives an `unknown` result:
+If you are using the state of a platform that takes extra time to load, the Template Sensor may get an `unknown` state during startup. To avoid this (and the resulting error messages in your log file), you can use `is_state()` function in your template. For example, you would replace {% raw %}`{{ states.cover.source.state == 'open' }}`{% endraw %} with this equivalent that returns `true`/`false` and never gives an `unknown` result:
 
 {% raw %}`{{ is_state('switch.source', 'on') }}`{% endraw %}
 

source/_components/tuya.markdown

@@ -45,7 +45,7 @@ tuya:
 
 {% configuration %}
 username:
-  description: Your username to log in to Tuya. This may be your phone number.
+  description: Your username to log in to Tuya. This may be your phone number which needs to be enquoted as this is a string.
   required: true
   type: string
 password:
@@ -53,7 +53,7 @@ password:
   required: true
   type: string
 country_code:
-  description: "Your account [country code](https://www.countrycode.org/), e.g., 1 for USA or 86 for China."
+  description: "Your account [country code](https://www.countrycode.org/), e.g., 1 for USA or 86 for China, again enquoted."
   required: true
   type: string
 platform:

source/_components/updater.markdown

@@ -3,7 +3,7 @@ title: "Updater"
 description: "Detecting when Home Assistant updates are available."
 logo: home-assistant.png
 ha_category:
-  - binary_sensor
+  - Binary Sensor
 ha_qa_scale: internal
 ha_release: 0.8
 ---

source/_docs/configuration/packages.markdown

@@ -6,10 +6,6 @@ redirect_from: /topics/packages/
 
 Packages in Home Assistant provide a way to bundle different component's configuration together. We already learned about the two configuration styles (specifying platforms entries together or individually) on the [adding devices](/docs/configuration/devices/) page. Both of these configuration methods require you to create the integration key in the main `configuration.yaml` file. With packages we have a way to include different components, or different configuration parts using any of the `!include` directives introduced in [splitting the configuration](/docs/configuration/splitting_configuration).
 
-<div class='note tip'>
-Note that if you use packages for your configuration, the configuration reloading buttons in the configuration panel will not reload your packages.
-</div>
-
 Packages are configured under the core `homeassistant/packages` in the configuration and take the format of a package name (no spaces, all lower case) followed by a dictionary with the package config. For example, package `pack_1` would be created as:
 
 ```yaml

source/_docs/tools/dev-tools.markdown

@@ -21,7 +21,7 @@ Screenshot of Home Assistant's Developer Tools.
 ## What can I do with Developer Tools?
 The Developer Tools is meant for **all** (not just for the developers) to quickly try out things - like calling services, update states, raising events, and publish messages in mqtt…etc.). It is also a necessary tool for those who write custom automations and scripts by hand. The following describes each of the section in detail.
 
-Services
+## Services
 
 This section is used to call Services that are available in the ServiceRegistry.
 
@@ -45,7 +45,7 @@ To turn on a light bulb, use the following steps:
   "rgb_color": [255, 0, 0]
 }
 ```
-States
+## States
 
 This section shows all the available entities, their corresponding state and the attribute values. The state and the attribute information is what Home Assistant sees at run time. To update the entity with a new state, or a new attribute value, click on the entity, scroll to the top, and modify the values, and click on “SET STATE” button.
 
@@ -53,7 +53,7 @@ Note that this is the state representation of a device within Home Assistant. Th
 
 For ex: Changing the `light.bedroom` state from `off` to `on` does not turn on the light. If there is an automation that triggers on the `state` change of the `light.bedroom`, it will be triggered – even though the actual bulb has not turned on. Also, when the bulb state changes – the state information will be overridden. In other words, the changes that are made through the “States” section are temporary, and is recommended to use for testing purposes only.
 
-Events
+## Events
 
 This Events section is as basic as it can get. It does only one thing – fires events on the event bus.
 To fire an event, simply type the name of the event, and pass the event data in JSON format.
@@ -75,7 +75,7 @@ If there is an automation that handles that event, it will be automatically trig
         message: "Light is turned {{ trigger.event.data.state }}"
 ```
 
-Template Editor
+## Template Editor
 
 The Template Editor provides a way to test the template code quickly. When the Template Editor page is loaded, it comes with a sample template code that illustrates how the code can be written and tested.
 
@@ -86,12 +86,12 @@ It is a good practice to test the template code in the template editor prior to
 For more information about jinja2, visit [jinja2 documentation](http://jinja.pocoo.org/docs/dev/templates/), and also read templating document [here](/topics/templating/)
 
 
-mqtt
+## MQTT
 
 This section is only visible if the MQTT integration is configured. To configure MQTT, add `mqtt:` to the `configuration.yaml` file. For more information, refer to the [mqtt](/components/mqtt/) component.
 
 Even though MQTT in general provides deeper functionality, the developer tools section of MQTT is limited to publishing messages to a given topic. It supports templates for the payload. To publish a message, simply specify the topic name and the payload and click “PUBLISH” button.
 
-Info
+## Info
 
 The Information tab simply provides information about the current installed version, additional links and credits. The tab also contains a section that shows `syslog` information, and the contents of `home-assistant.log` with an option to clear and refresh the logs.

source/_docs/z-wave/controllers.markdown

@@ -34,6 +34,7 @@ The alternative to a stick is a hub that supports Z-Wave. Home Assistant support
  - [Vera](/components/vera/)
  - [Wink](/components/wink/)
  - [Fibaro](/components/fibaro/)
+ - [SmartThings](/components/smartthings/)
 
 ## Controller Notes
 

source/_posts/2019-09-17-happy-birthday.markdown

@@ -0,0 +1,74 @@
+---
+layout: post
+title: "Happy 6th Birthday"
+description: "Thank you community for making Home Assistant a special place."
+date: 2019-09-17 01:11:03
+date_formatted: "September 17, 2019"
+author: Paulus Schoutsen
+author_twitter: balloob
+comments: true
+categories: Announcements
+og_image: /images/blog/2019-09-birthday/social.png
+---
+
+<img src='/images/blog/2019-09-birthday/top.png' style='border: 0;box-shadow: none;'>
+
+### Dear community, happy sixth birthday.
+
+#### It has been six amazing years
+
+Thanks to all the people working on the core of Home Assistant.
+
+Thanks to all the people working on the Home Assistant frontend.
+
+Thanks to all the people working on Hass.io.
+
+Thanks to all the people workin on the mobile apps.
+
+Thanks to all the people working on Hass.io add-ons.
+
+Thanks to all the people who help with design and user stories.
+
+Thanks to all the people who make the documentation possible.
+
+Thanks to all the people active on the forums.
+
+Thanks to all the people active in the chat rooms.
+
+Thanks to all the people active on social media.
+
+Thanks to all the people making videos helping people use Home Assistant.
+
+Thanks to all the people making videos sharing their achievements using Home Assistant.
+
+Thanks to all the people writing blog posts about Home Assistant.
+
+Thanks to all the people invovled in making the Home Asssistant Podcast.
+
+Thanks to all the people moderating our community, maintaining its high quality.
+
+Thanks to all the people working on running our infrastructure.
+
+Thanks to all the people who help out with code reviews and maintaining our code quality.
+
+Thanks to all the people building and sharing cool frontends build with Lovelace.
+
+Thanks to all the people creating and sharing custom Lovelace cards.
+
+Thanks to all the people creating and sharing custom components.
+
+Thanks to all the manufacturers that work on integrating with Home Assistant.
+
+Thanks to all the companies providing the Home Assistant project with resources: Nabu Casa, GitHub/Azure/Microsoft, CloudFlare, Netlify, Lokalise.co, CARTO.
+
+Thanks to the Material Design Icons team for beautiful icons.
+
+Thanks to all the people who support Home Assistant by subscribing to Home Assistant Cloud.
+
+Thanks to all the people who share the Home Assistant love.
+
+Thanks.
+
+❤️
+
+Paulus

source/hassio/installation.markdown

@@ -15,8 +15,8 @@ The following will take you through the steps required to install Hass.io.
      - [Raspberry Pi 2 Model B][pi2]
      - [Raspberry Pi 3 Model B and B+ 32bit][pi3-32] (recommended)
      - [Raspberry Pi 3 Model B and B+ 64bit][pi3-64]
-     - [(Beta) Raspberry Pi 4 Model B 32bit][pi4-32] (recommended)
+     - [(RC) Raspberry Pi 4 Model B 32bit][pi4-32] (recommended)
-     - [(Beta) Raspberry Pi 4 Model B 64bit][pi4-64]
+     - [(RC) Raspberry Pi 4 Model B 64bit][pi4-64]
      - [Tinkerboard][tinker]
      - [Odroid-C2][odroid-c2]
      - [Odroid-XU4][odroid-xu4]
@@ -180,7 +180,7 @@ curl -sL "https://raw.githubusercontent.com/home-assistant/hassio-installer/mast
  - `raspberrypi3-64`
  - `odroid-c2`
  - `odroid-cu2`
- - `odriod-xu`
+ - `odroid-xu`
  - `orangepi-prime`
 
 <div class='note'>
@@ -197,8 +197,8 @@ A detailed guide about running Hass.io as a virtual machine is available in the
 [pi2]: https://github.com/home-assistant/hassos/releases/download/2.12/hassos_rpi2-2.12.img.gz
 [pi3-32]: https://github.com/home-assistant/hassos/releases/download/2.12/hassos_rpi3-2.12.img.gz
 [pi3-64]: https://github.com/home-assistant/hassos/releases/download/2.12/hassos_rpi3-64-2.12.img.gz
-[pi4-32]: https://github.com/home-assistant/hassos/releases/download/3.4/hassos_rpi4-3.4.img.gz
+[pi4-32]: https://github.com/home-assistant/hassos/releases/download/3.5/hassos_rpi4-3.5.img.gz
-[pi4-64]: https://github.com/home-assistant/hassos/releases/download/3.4/hassos_rpi4-64-3.4.img.gz
+[pi4-64]: https://github.com/home-assistant/hassos/releases/download/3.5/hassos_rpi4-64-3.5.img.gz
 [tinker]: https://github.com/home-assistant/hassos/releases/download/2.12/hassos_tinker-2.12.img.gz
 [odroid-c2]: https://github.com/home-assistant/hassos/releases/download/2.12/hassos_odroid-c2-2.12.img.gz
 [odroid-xu4]: https://github.com/home-assistant/hassos/releases/download/2.12/hassos_odroid-xu4-2.12.img.gz