Merge branch 'current' into next

CODEOWNERS

@@ -9,6 +9,7 @@
 
 # Pages
 source/_integrations/abode.markdown @shred86
+source/_integrations/acmeda.markdown @atmurray
 source/_integrations/adguard.markdown @frenck
 source/_integrations/agent_dvr.markdown @ispysoftware
 source/_integrations/airly.markdown @bieniu
@@ -38,7 +39,6 @@ source/_integrations/atome.markdown @baqs
 source/_integrations/august.markdown @bdraco
 source/_integrations/aurora_abb_powerone.markdown @davet2001
 source/_integrations/auth.markdown @home-assistant/core
-source/_integrations/automatic.markdown @armills
 source/_integrations/automation.markdown @home-assistant/core
 source/_integrations/avea.markdown @pattyland
 source/_integrations/avri.markdown @timvancann
@@ -64,6 +64,7 @@ source/_integrations/bt_smarthub.markdown @jxwolstenholme
 source/_integrations/buienradar.markdown @mjj4791 @ties
 source/_integrations/cast.markdown @emontnemery
 source/_integrations/cert_expiry.markdown @Cereal2nd @jjlawren
+source/_integrations/circuit.markdown @braam
 source/_integrations/cisco_ios.markdown @fbradyirl
 source/_integrations/cisco_mobility_express.markdown @fbradyirl
 source/_integrations/cisco_webex_teams.markdown @fbradyirl
@@ -82,7 +83,7 @@ source/_integrations/cups.markdown @fabaff
 source/_integrations/daikin.markdown @fredrike
 source/_integrations/darksky.markdown @fabaff
 source/_integrations/deconz.markdown @Kane610
-source/_integrations/delijn.markdown @bollewolle
+source/_integrations/delijn.markdown @bollewolle @Emilv2
 source/_integrations/demo.markdown @home-assistant/core
 source/_integrations/denonavr.markdown @scarface-4711 @starkillerOG
 source/_integrations/derivative.markdown @afaucogney
@@ -93,6 +94,7 @@ source/_integrations/directv.markdown @ctalkington
 source/_integrations/discogs.markdown @thibmaek
 source/_integrations/doorbird.markdown @oblogic7 @bdraco
 source/_integrations/dsmr_reader.markdown @depl0y
+source/_integrations/dunehd.markdown @bieniu
 source/_integrations/dweet.markdown @fabaff
 source/_integrations/dynalite.markdown @ziv1234
 source/_integrations/dyson.markdown @etheralm
@@ -144,6 +146,7 @@ source/_integrations/gios.markdown @bieniu
 source/_integrations/gitter.markdown @fabaff
 source/_integrations/glances.markdown @fabaff @engrbm87
 source/_integrations/gntp.markdown @robbiet480
+source/_integrations/gogogate2.markdown @vangorra
 source/_integrations/google_assistant.markdown @home-assistant/cloud
 source/_integrations/google_cloud.markdown @lufton
 source/_integrations/google_translate.markdown @awarecan
@@ -154,6 +157,7 @@ source/_integrations/griddy.markdown @bdraco
 source/_integrations/group.markdown @home-assistant/core
 source/_integrations/growatt_server.markdown @indykoning
 source/_integrations/gtfs.markdown @robbiet480
+source/_integrations/guardian.markdown @bachya
 source/_integrations/harmony.markdown @ehendrix23 @bramkragten @bdraco
 source/_integrations/heatmiser.markdown @andylockran
 source/_integrations/heos.markdown @andrewsayre
@@ -172,7 +176,7 @@ source/_integrations/homematicip_cloud.markdown @SukramJ
 source/_integrations/honeywell.markdown @zxdavb
 source/_integrations/html5.markdown @robbiet480
 source/_integrations/http.markdown @home-assistant/core
-source/_integrations/huawei_lte.markdown @scop
+source/_integrations/huawei_lte.markdown @scop @fphammerle
 source/_integrations/huawei_router.markdown @abmantis
 source/_integrations/hue.markdown @balloob
 source/_integrations/hunterdouglas_powerview.markdown @bdraco
@@ -187,6 +191,7 @@ source/_integrations/input_datetime.markdown @home-assistant/core
 source/_integrations/input_number.markdown @home-assistant/core
 source/_integrations/input_select.markdown @home-assistant/core
 source/_integrations/input_text.markdown @home-assistant/core
+source/_integrations/insteon.markdown @teharris1
 source/_integrations/integration.markdown @dgomes
 source/_integrations/intesishome.markdown @jnimmo
 source/_integrations/ios.markdown @robbiet480
@@ -297,11 +302,11 @@ source/_integrations/pilight.markdown @trekky12
 source/_integrations/plaato.markdown @JohNan
 source/_integrations/plant.markdown @ChristianKuehnel
 source/_integrations/plex.markdown @jjlawren
-source/_integrations/plugwise.markdown @laetificat @CoMPaTech @bouwew
+source/_integrations/plugwise.markdown @CoMPaTech @bouwew
 source/_integrations/plum_lightpad.markdown @ColinHarrington
 source/_integrations/point.markdown @fredrike
 source/_integrations/powerwall.markdown @bdraco @jrester
-source/_integrations/proxmoxve.markdown @k4ds3
+source/_integrations/proxmoxve.markdown @k4ds3 @jhollowe
 source/_integrations/ps4.markdown @ktnrg45
 source/_integrations/ptvsd.markdown @swamp-ig
 source/_integrations/push.markdown @dgomes
@@ -361,7 +366,6 @@ source/_integrations/soma.markdown @ratsept
 source/_integrations/somfy.markdown @tetienne
 source/_integrations/sonarr.markdown @ctalkington
 source/_integrations/songpal.markdown @rytilahti @shenxn
-source/_integrations/sonos.markdown @amelchio
 source/_integrations/spaceapi.markdown @fabaff
 source/_integrations/speedtestdotnet.markdown @rohankapoorcom
 source/_integrations/spider.markdown @peternijssen

_config.yml

@@ -100,9 +100,9 @@ social:
 
 # Home Assistant release details
 current_major_version: 0
-current_minor_version: 110
+current_minor_version: 111
-current_patch_version: 7
+current_patch_version: 2
-date_released: 2020-06-09
+date_released: 2020-06-13
 
 # Either # or the anchor link to latest release notes in the blog post.
 # Must be prefixed with a # and have double quotes around it.

source/_integrations/api.markdown

@@ -10,7 +10,7 @@ ha_codeowners:
 ha_domain: api
 ---
 
-The `api` integration exposes a RESTful API and allows one to interact with a Home Assistant instance that is running headless. This integration depends on the [`http` integration](/integrations/http/).
+The `api` integration exposes a RESTful API and allows one to interact with a Home Assistant instance that is running headless. This integration depends on the [HTTP integration](/integrations/http/).
 
 ```yaml
 # Example configuration.yaml entry

source/_integrations/binary_sensor.modbus.markdown

@@ -74,13 +74,14 @@ Example a sensor with a 10 seconds scan interval:
 binary_sensor:
   - platform: modbus
     scan_interval: 10
-    coils:
+    inputs:
       - name: Sensor1
         hub: hub1
         slave: 1
-        coil: 100
+        address: 100
       - name: Sensor2
         hub: hub1
         slave: 1
-        coil: 110
+        address: 110
+        input_type: discrete_input
 ```

source/_integrations/bsblan.markdown

@@ -3,11 +3,11 @@ title: BSB-Lan
 description: Instructions on how to integrate BSBLan device into Home Assistant.
 logo: bsblan.png
 ha_category: Climate
-ha_release: "0.110"
+ha_release: '0.110'
 ha_iot_class: Local Polling
 ha_config_flow: true
 ha_codeowners:
-  - "@liudger"
+  - '@liudger'
 ha_domain: bsblan
 ---
 

source/_integrations/cpuspeed.markdown

@@ -15,7 +15,7 @@ The `cpuspeed` sensor platform to allow you to monitor the current CPU speed.
 
 <div class='note warning'>
 
-  You can't use this sensor in a Container (like Hass.io) as it requires access to the physical CPU. Also, not all [ARM CPUs](https://github.com/workhorsy/py-cpuinfo/#cpu-support) are supported.
+  You can't use this sensor in a container (only Home Assistant Core is supported) as it requires access to the physical CPU. Also, not all [ARM CPUs](https://github.com/workhorsy/py-cpuinfo/#cpu-support) are supported.
 
 </div>
 

source/_integrations/delijn.markdown

@@ -8,6 +8,7 @@ ha_category:
 ha_iot_class: Cloud Polling
 ha_codeowners:
   - '@bollewolle'
+  - '@Emilv2'
 ha_domain: delijn
 ---
 

source/_integrations/gogogate2.markdown

@@ -7,6 +7,9 @@ ha_category:
 ha_release: 0.67
 ha_iot_class: Local Polling
 ha_domain: gogogate2
+ha_codeowners:
+  - '@vangorra'
+ha_config_flow: true
 ---
 
 The GogoGate2 integration lets you control Gogogate2-Enabled garage doors through Home Assistant. Device names in Home Assistant are generated based on the names defined in your Gogogate2 mobile app.

source/_integrations/guardian.markdown

@@ -1,7 +1,7 @@
 ---
-title: Guardian
+title: Elexa Guardian
 description: Instructions on how to integrate SimpliSafe into Home Assistant.
-ha_release: "0.111"
+ha_release: '0.111'
 ha_category:
   - Binary Sensor
   - Sensor

source/_integrations/huawei_lte.markdown

@@ -13,6 +13,7 @@ ha_iot_class: Local Polling
 ha_config_flow: true
 ha_codeowners:
   - '@scop'
+  - '@fphammerle'
 ha_domain: huawei_lte
 ---
 

source/_integrations/insteon.markdown

@@ -12,6 +12,8 @@ ha_category:
 ha_iot_class: Local Push
 ha_release: 0.39
 ha_domain: insteon
+ha_codeowners:
+  - '@teharris1'
 ---
 
 This integration adds "local push" support for INSTEON Modems allowing linked INSTEON devices to be used within Home Assistant.

source/_integrations/lutron_caseta.markdown

@@ -14,7 +14,6 @@ ha_iot_class: Local Push
 ha_domain: lutron_caseta
 ha_codeowners:
   - '@swails'
-ha_config_flow: true
 ---
 
 [Lutron](http://www.lutron.com/) is an American lighting control company. They have several lines of home automation devices that manage light switches, dimmers, occupancy sensors, HVAC controls, etc. The `lutron_caseta` integration in Home Assistant is responsible for communicating with the Lutron Caseta Smart Bridge for the [Caseta](https://www.casetawireless.com/) product line of dimmers, switches, shades, and sensors. It will also communicate with the Lutron Radio RA2 Main Repeater for the [RA2 Select](http://www.lutron.com/en-US/Products/Pages/WholeHomeSystems/RA2Select/Overview.aspx) product line of dimmers, switches, shades, and sensors.

source/_integrations/plugwise.markdown

@@ -5,7 +5,7 @@ ha_category:
   - Climate
   - Sensor
   - Switch
-  - Water_heater
+  - Water Heater
 ha_iot_class: Local Polling
 ha_release: 0.98
 ha_codeowners:
@@ -15,8 +15,8 @@ ha_config_flow: true
 ha_domain: plugwise
 ---
 
-This enables [Plugwise](https://plugwise.com) components with a central Smile gateway to be integrated. This integration talks locally to your **Smile** interface, and you will need its password and IP address.
+This enables [Plugwise](https://www.plugwise.com) components with a central Smile gateway to be integrated. This integration talks locally to your **Smile** interface, and you will need its password and IP address.
-The platform supports [Anna](https://www.plugwise.com/en_US/products/anna), [Adam (zonecontrol)](https://plugwise.com/en_US/zone_control) and [P1](https://plugwise.com/en_us/products/smile-p1) Smile products. See below list for more details.
+The platform supports [Anna](https://www.plugwise.com/en_US/products/anna), [Adam (zonecontrol)](https://www.plugwise.com/en_US/zonecontrol) and [P1](https://www.plugwise.com/en_US/products/smile-p1) Smile products. See below list for more details.
 
 Platforms available - depending on your Smile and setup are include:
 

source/_integrations/sonos.markdown

@@ -8,8 +8,6 @@ ha_release: 0.7.3
 ha_iot_class: Local Push
 ha_config_flow: true
 ha_domain: sonos
-ha_codeowners:
-  - '@amelchio'
 ---
 
 The `sonos` integration allows you to control your [Sonos](https://www.sonos.com) wireless speakers from Home Assistant. It also works with IKEA Symfonisk speakers.

source/_integrations/synology.markdown

@@ -25,7 +25,7 @@ To enable your Surveillance Station cameras in your installation, add the follow
 # Minimum configuration.yaml entry
 camera:
   - platform: synology
-    url: IP_ADDRESS_OF_SYNOLOGY_NAS
+    url: FULL_URL_OF_SYNOLOGY_NAS
     username: YOUR_USERNAME
     password: YOUR_PASSWORD
 ```

source/_integrations/tado.markdown

@@ -127,3 +127,16 @@ Find your `home_id` by browsing to `https://my.tado.com/api/v2/me?username=YOUR_
 ```
 
 In this example `12345` is the `home_id` you'll need to configure.
+
+### Finding your `home_id` alternative
+
+If the above method returns an unauthorized error. The `home_id` can also be found using Chrome developer tools. Whilst logged into https://my.tado.com/webapp, take the following steps: 
+
+- Select the "Networ"' tab
+- Filter for "home"
+- Under "Name", select "users"
+- Click on the "Response" tab
+
+The `home_id` appears in the response for users as `"id":12345`
+
+In this example `12345` is the `home_id` you'll need to configure.

source/_integrations/vacuum.xiaomi_miio.markdown

@@ -279,7 +279,7 @@ This token (32 hexadecimal characters) is required for the Xiaomi Mi Robot Vacuu
 ### iOS
 
 1. Configure the robot with the Mi Home app. Make sure to select the correct region, as Xiaomi uses different product names for different geographical areas. Note that the new RoboRock app is currently not supported for this method.
-2. Using iTunes, create an unencrypted backup of your iPhone.
+2. Using iTunes, create an unencrypted backup of your iPhone. Since macOS 10.15 there is no iTunes app. Use Finder instead - after connecting your iOS device you should see it in left menu of Finder window. 
 3. Install [iBackup Viewer](https://www.imactools.com/iphonebackupviewer/), open it, and open your backup.
 4. Open the "Raw Data" module.
 5. Navigate to `com.xiaomi.mihome`.
@@ -368,6 +368,8 @@ Where params specify room numbers, for multiple rooms, params can be specified l
 
 Valid room numbers can be retrieved using miio command-line tool. It will only give room numbers and not the room names. To get the room names, one can just test the app_segment_clean command and see which room it cleans.
 
+Note: if you don't have access to the miio command-line tool, you can try the app_segment_clean command starting from number 16 as this number seems to be the first room.
+
 ```bash
 miio protocol call <ip of the vacuum> get_room_mapping
 ```

source/_lovelace/media-control.markdown

@@ -20,6 +20,11 @@ entity:
   required: true
   description: "A media player `entity_id`."
   type: string
+name:
+  required: false
+  description: Overwrites friendly name.
+  type: string
+  default: Name of Entity
 {% endconfiguration %}
 
 ## Example

source/hassio/installation.markdown

@@ -9,34 +9,34 @@ The following will take you through the steps required to install Home Assistant
 
    - As an image for your device:
 
-     - [Raspberry Pi 3 Model B and B+ 32bit][pi3-32] (recommended)
+     - [Raspberry Pi 3 Model B and B+ 32-bit][pi3-32] (recommended)
-     - [Raspberry Pi 3 Model B and B+ 64bit][pi3-64]
+     - [Raspberry Pi 3 Model B and B+ 64-bit][pi3-64]
-     - [Raspberry Pi 4 Model B 32bit][pi4-32] (recommended)
+     - [Raspberry Pi 4 Model B (1 GB, 2 GB and 4 GB model) 32-bit][pi4-32] (recommended)
-     - [Raspberry Pi 4 Model B 64bit][pi4-64]
+     - [Raspberry Pi 4 Model B (1 GB, 2 GB and 4 GB model) 64-bit][pi4-64]
      - [Tinkerboard][tinker]
-     - [Odroid-C2][odroid-c2]
+     - [Odroid-C2][odroid-c2], [Odroid-N2][odroid-n2], [Odroid-XU4][odroid-xu4]
-     - [Odroid-N2][odroid-n2]
+     - [Intel NUC][intel-nuc]
-     - [Odroid-XU4][odroid-xu4]
-     - [Intel-Nuc][intel-nuc]
 
    - As a virtual appliance (x86_64/UEFI):
   
-     - [VMDK][vmdk]
+     - [VMDK][vmdk], [VHDX][vhdx], [VDI][vdi], [QCOW2][qcow2], [OVA][Virtual Appliance]
-     - [VHDX][vhdx]
-     - [VDI][vdi]
-     - [QCOW2][qcow2]
-     - [OVA][Virtual Appliance]
 
-   - Not recommended Hardware:
+   - Not yet supported hardware:
 
-     - [Raspberry Pi][pi1]
+     - Raspberry Pi 4 Model B (8 GB model)
-     - [Raspberry Pi Zero-W][pi0-w]
+
-     - [Raspberry Pi 2][pi2]
+   - Not recommended hardware:
+
+     - [Raspberry Pi][pi1], [Raspberry Pi Zero-W][pi0-w], [Raspberry Pi 2][pi2]
 
 2. Install Home Assistant:
 
    - Flash the downloaded image to an SD card using [balenaEtcher][balenaEtcher]. If using a Pi, we recommend at least a 32 GB SD card to avoid running out of space.
-   - Load the appliance image into your virtual machine software. Allow at least 32 GB of disk space for the virtual machine. Choose 64-bit Linux and UEFI boot. For a KVM-based setup with `virt-manager`, set **Firmware** to `UEFI x86_64: /usr/share/ovmf/x64/OVMF_CODE.fd`.
+   - Load the appliance image into your virtual machine software. (Note: You are free to assign as much resources as you wish to the VM, please assign enough based on your add-on needs)
+     - For VirtualBox create a new virtual machine, select "Other Linux (64Bit), assign it atleast 2 GB of memory and "Use an existing virtual hard disk file", select the VDI file from above, afterwards edit the "Settings" of the VM and go "System" then Motherboard and Enable EFI, then "Network" "Adapter 1" Bridged and your adapter
+     - For Hyper-V create a new virtual machine, select "Generation 2", assign it at least 2 GB of memory and select "Connection -> "Your Virtual Switch that is bridged", then "Use an existing virtual hard disk" and select the VHDX file from above, after creation go to "Settings" -> "Security" and deselect "Enable Secure Boot"
+     - For KVM create a new virtual machine in `virt-manager`, select "Import existing disk image", provide the path to the QCOW2 image above, choose "Generic Default" for the operating system, assign at least 2 GB memory and 1 vCPU, check the box for "Customize configuration before install" and select your bridge under "Network Selection", then under customization select "Overview" -> "Firmware" -> "UEFI x86_64: ...".
+     - For Vmware Workstation create a new virtual machine, select "Custom", make it compatible with the default of Workstation and ESX, Choose "I will install the operating system later", select "Linux" -> "Other Linux 5.x or later kernel 64-bit", give it atleast 2GB RAM and 1vCPU, select "Use Bridged Networking" then "Use an existing virtual disk" and select the VMDK file above, after creation of VM go to "Settings" and "Options" then "Advanced" and select "Firmware type" to "UEFI"
 
 3. Optional - set up the Wi-Fi or a static IP address. There are two possible places for that:
    - on a blank USB stick with a FAT32 partition having partition label `CONFIG`, while in its root directory, create the `network/my-network` file, or