Merge branch 'current' into next

Gemfile.lock

@@ -79,7 +79,7 @@ GEM
       forwardable-extended (~> 2.6)
     public_suffix (4.0.7)
     racc (1.6.0)
-    rack (2.2.3.1)
+    rack (2.2.4)
     rack-protection (2.2.0)
       rack
     rake (13.0.6)

source/_includes/installation/operating_system.md

@@ -213,8 +213,8 @@ Load the appliance image into your virtual machine hypervisor. (Note: You are fr
 
 Minimum recommended assignments:
 
-- 2GB RAM
-- 32GB Storage
+- 2 GB RAM
+- 32 GB Storage
 - 2vCPU
 
 _All these can be extended if your usage calls for more resources._
@@ -241,18 +241,24 @@ _All these can be extended if your usage calls for more resources._
 
     </div>
 
-- title: KVM
+- title: KVM (virt-manager)
   content: |
     1. Create a new virtual machine in `virt-manager`
     2. Select “Import existing disk image”, provide the path to the QCOW2 image above
     3. Choose “Generic Default” for the operating system
     4. Check the box for “Customize configuration before install”
     5. Select your bridge under “Network Selection”
-    6. Under customization select “Overview” -> “Firmware” -> “UEFI x86_64: …”
+    6. Under customization select “Overview” -> “Firmware” -> “UEFI x86_64: ...”
     7. Click "Add Hardware" (bottom left), and select "Channel"
     8. Select device type: "unix"
     9. Select name: "org.qemu.guest_agent.0"
-    10. Finally select "Begin Instalation" (upper left corner)
+    10. Finally select "Begin Installation" (upper left corner)
+
+- title: KVM (virt-install)
+  content: |
+    ```bash
+    virt-install --name hass --description "Home Assistant OS" --os-variant=generic --ram=2048 --vcpus=2 --disk <PATH TO QCOW2 FILE>,bus=sata --graphics none --boot uefi
+    ```
 
 {% if page.installation_type == 'windows' or page.installation_type == 'linux' %}
 

source/_integrations/application_credentials.markdown

@@ -12,15 +12,24 @@ ha_integration_type: integration
 
 The Application Credentials integration is used by integrations that use OAuth2 to link your account to Home Assistant. The most common and preferred approach is using account linking with Home Assistant Cloud, however not all cloud providers support that and integrations can use Application Credentials instead. Additionally, users may use Application Credentials if preferred instead of Home Assistant Cloud Account Linking.
 
+## Automatic Setup
+
+Some integrations like [Google Calendar](/integrations/google/) will automatically create application credentials as part of adding an integration. To view any entries:
+1. Go to **{% my integrations title="Settings -> Devices & Services" %}**
+2. Click the overflow menu **...** and choose **Application Credentials**
+
+![Application credential list](/images/integrations/application_credentials/application-credentials.png)
+
 ## Manual Setup
 
 Note that integrations that do not support cloud linking will prompt to setup Application Credentials
 when setting up for the first time. You may also manually enter credentials with the following steps:
 
 1. Obtain an OAuth *Client ID* and *Client Secret* from the cloud provider. The integration should have specific instructions for this.
-2. In Home Assistant navigate to **Settings** -> **Devices & Services**
+2. In Home Assistant navigate to **{% my integrations title="Settings -> Devices & Services" %}**
 3. Click the overflow menu **...** and choose **Application Credentials**
 4. Select the integration, enter a *Name* and your OAuth *Client ID* and *Client Secret*.
 5. Save the credentials
 
+![Manual setup](/images/integrations/application_credentials/application-credential-setup.png)
 You may then visit **Integrations** and setup the integration.

source/_integrations/fritzbox.markdown

@@ -37,15 +37,15 @@ There is currently support for the following device types within Home Assistant:
 
 #### Tested Devices
 
-- [FRITZ!Box 6490 Cable](https://en.avm.de/products/fritzbox/fritzbox-6490-cable/)
+- FRITZ!Box 6490 Cable
 - [FRITZ!Box 6591 Cable](https://en.avm.de/products/fritzbox/fritzbox-6591-cable/)
 - [FRITZ!Box 7590](https://en.avm.de/products/fritzbox/fritzbox-7590/)
-- [FRITZ!Box 7490](https://en.avm.de/service/fritzbox/fritzbox-7490/overview/)
-- [FRITZ!Box 7430](https://en.avm.de/service/fritzbox/fritzbox-7430/overview/)
+- FRITZ!Box 7490
+- FRITZ!Box 7430
 - [FRITZ!DECT 200](https://en.avm.de/products/fritzdect/fritzdect-200/)
 - [FRITZ!DECT 301](https://en.avm.de/products/fritzdect/fritzdect-301/)
 - [FRITZ!DECT 500](https://en.avm.de/products/fritzdect/fritzdect-500/)
-- [Eurotronic Comet DECT](https://eurotronic.org/produkte/elektronische-heizkoerperthermostate/sparmatic-comet/)
+- [Eurotronic Comet DECT](https://eurotronic.org/produkte/dect-ule-heizkoerperthermostat/comet-dect/)
 - [Magenta SmartHome LED E27](https://www.smarthome.de/geraete/smarthome-led-lampe-e27-farbig-weiss)
 
 {% include integrations/config_flow.md %}

source/_integrations/nmap_tracker.markdown

@@ -51,14 +51,4 @@ Raw configurable scan options for Nmap:
   default: -F T4 --min-rate 10 --host-timeout 5s
 {% endconfiguration_basic %}
 
-### Linux capabilities
-
-On Linux systems (such as the Home Assistant Operating System) you can extend the functionality of Nmap, without having to run it as root, by using *Linux capabilities*. Be sure to specify the full path to wherever you installed Nmap:
-
-```bash
-sudo setcap cap_net_raw,cap_net_admin,cap_net_bind_service+eip /usr/bin/nmap
-```
-
-And you can set up the device tracker scan options with `--privileged -sn`
-
 See the [device tracker integration page](/integrations/device_tracker/) for instructions how to configure the people to be tracked.

source/_integrations/spotify.markdown

@@ -22,6 +22,7 @@ The Spotify media player integration allows you to control [Spotify](https://www
 
 - Spotify account
 - (Optional) Spotify developer application configured for Home Assistant (see [below](#create-a-spotify-application))
+- Spotify compatible playback [source](#selecting-output-source) device
 
 <div class='note'>
   Spotify integrated media controls (pause, play, next, etc.) require a Premium account.
@@ -80,6 +81,20 @@ accounts can be linked to a _single_ Spotify application. You will have to add t
 To add an additional Spotify account to Home Assistant, go to the Spotify website and log out, then repeat _only_ the steps
 in the [Configuration](#configuration) section. 
 
+## Selecting output source
+
+To play media Spotify first needs a device selected for audio output known as the `source`.
+
+```yaml
+# Example code to select an AV receiver as the output device
+service: media_player.select_source
+entity_id: media_player.spotify
+data:
+  source: "Denon AVR-X2000"
+```
+
+The Spotify API cannot initiate playback to a device not already known to the Spotify API. The source list of available devices can be found in the Details section of the Spotify Media Player Control and the `source_list` attribute in the {% my developer_states title="Developer Tools States" %}.
+
 ## Playing Spotify playlists
 
 You can send playlists to Spotify using the `"media_content_type": "playlist"`, which is part of the
@@ -98,7 +113,7 @@ script:
           media_content_type: playlist
 ```
 
-The `media_content_id` value can be obtained from the Spotify desktop app by clicking on the more options ("...") next to the album art picture, selecting "Share" and then "Copy Spotify URI" or "Copy Playlist Link" (also available in the Spotify phone and web app).
+The `media_content_id` value can be obtained from the Spotify desktop app by clicking on the more options ("...") next to the album art picture, selecting "Share" and then "Copy Spotify URI" or "Copy Playlist Link" (also available in the Spotify phone and web app). Alternatively a Spotify URI string (e.g. `spotify:playlist:5xddIVAtLrZKtt4YGLM1SQ`) can be supplied for the `media_content_id`.
 
 ## Unsupported Devices