Merge branch 'current' into next

CODEOWNERS

@@ -9,6 +9,7 @@
 
 # Pages
 source/_integrations/abode.markdown @shred86
+source/_integrations/accuweather.markdown @bieniu
 source/_integrations/acmeda.markdown @atmurray
 source/_integrations/adguard.markdown @frenck
 source/_integrations/agent_dvr.markdown @ispysoftware
@@ -44,6 +45,7 @@ source/_integrations/avri.markdown @timvancann
 source/_integrations/awair.markdown @ahayworth @danielsjf
 source/_integrations/aws.markdown @awarecan
 source/_integrations/axis.markdown @Kane610
+source/_integrations/azure_devops.markdown @timmo001
 source/_integrations/azure_event_hub.markdown @eavanvalkenburg
 source/_integrations/azure_service_bus.markdown @hfurubotten
 source/_integrations/beewi_smartclim.markdown @alemuro
@@ -73,6 +75,7 @@ source/_integrations/cloudflare.markdown @ludeeus
 source/_integrations/comfoconnect.markdown @michaelarnauts
 source/_integrations/config.markdown @home-assistant/core
 source/_integrations/configurator.markdown @home-assistant/core
+source/_integrations/control4.markdown @lawtancool
 source/_integrations/conversation.markdown @home-assistant/core
 source/_integrations/coolmaster.markdown @OnFreund
 source/_integrations/coronavirus.markdown @home_assistant/core
@@ -95,8 +98,10 @@ source/_integrations/digital_ocean.markdown @fabaff
 source/_integrations/directv.markdown @ctalkington
 source/_integrations/discogs.markdown @thibmaek
 source/_integrations/doorbird.markdown @oblogic7 @bdraco
+source/_integrations/dsmr.markdown @Robbie1221
 source/_integrations/dsmr_reader.markdown @depl0y
 source/_integrations/dunehd.markdown @bieniu
+source/_integrations/dwd_weather_warnings.markdown @runningman84 @stephan192 @Hummel95
 source/_integrations/dweet.markdown @fabaff
 source/_integrations/dynalite.markdown @ziv1234
 source/_integrations/dyson.markdown @etheralm
@@ -106,10 +111,11 @@ source/_integrations/edl21.markdown @mtdcr
 source/_integrations/egardia.markdown @jeroenterheerdt
 source/_integrations/eight_sleep.markdown @mezz64
 source/_integrations/elgato.markdown @frenck
-source/_integrations/elkm1.markdown @bdraco
+source/_integrations/elkm1.markdown @gwww @bdraco
 source/_integrations/elv.markdown @majuss
 source/_integrations/emby.markdown @mezz64
 source/_integrations/emoncms.markdown @borpin
+source/_integrations/emulated_kasa.markdown @kbickar
 source/_integrations/enigma2.markdown @fbradyirl
 source/_integrations/enocean.markdown @bdurrer
 source/_integrations/entur_public_transport.markdown @hfurubotten
@@ -124,8 +130,10 @@ source/_integrations/ezviz.markdown @baqs
 source/_integrations/fastdotcom.markdown @rohankapoorcom
 source/_integrations/file.markdown @fabaff
 source/_integrations/filter.markdown @dgomes
+source/_integrations/firmata.markdown @DaAwesomeP
 source/_integrations/fixer.markdown @fabaff
 source/_integrations/flick_electric.markdown @ZephireNZ
+source/_integrations/flo.markdown @dmulcahey
 source/_integrations/flock.markdown @fabaff
 source/_integrations/flume.markdown @ChrisMandich @bdraco
 source/_integrations/flunearyou.markdown @bachya
@@ -163,6 +171,7 @@ source/_integrations/hikvisioncam.markdown @fbradyirl
 source/_integrations/hisense_aehw4a1.markdown @bannhead
 source/_integrations/history.markdown @home-assistant/core
 source/_integrations/hive.markdown @Rendili @KJonline
+source/_integrations/hlk_sw16.markdown @jameshilliard
 source/_integrations/home_connect.markdown @DavidMStraub
 source/_integrations/homeassistant.markdown @home-assistant/core
 source/_integrations/homekit.markdown @bdraco
@@ -182,6 +191,7 @@ source/_integrations/iammeter.markdown @lewei50
 source/_integrations/iaqualink.markdown @flz
 source/_integrations/icloud.markdown @Quentame
 source/_integrations/ign_sismologia.markdown @exxamalte
+source/_integrations/image.markdown @home-assistant/core
 source/_integrations/incomfort.markdown @zxdavb
 source/_integrations/influxdb.markdown @fabaff @mdegat01
 source/_integrations/input_boolean.markdown @home-assistant/core
@@ -207,8 +217,8 @@ source/_integrations/keba.markdown @dannerph
 source/_integrations/keenetic_ndms2.markdown @foxel
 source/_integrations/kef.markdown @basnijholt
 source/_integrations/keyboard_remote.markdown @bendavid
-source/_integrations/knx.markdown @Julius2342
-source/_integrations/kodi.markdown @armills
+source/_integrations/knx.markdown @Julius2342 @farmio @marvin-w
+source/_integrations/kodi.markdown @OnFreund
 source/_integrations/konnected.markdown @heythisisnate @kit-klein
 source/_integrations/lametric.markdown @robbiet480
 source/_integrations/launch_library.markdown @ludeeus
@@ -218,6 +228,7 @@ source/_integrations/linux_battery.markdown @fabaff
 source/_integrations/local_ip.markdown @issacg
 source/_integrations/logger.markdown @home-assistant/core
 source/_integrations/logi_circle.markdown @evanjd
+source/_integrations/loopenergy.markdown @pavoni
 source/_integrations/luci.markdown @fbradyirl @mzdrale
 source/_integrations/luftdaten.markdown @fabaff
 source/_integrations/lupusec.markdown @majuss
@@ -226,14 +237,15 @@ source/_integrations/lutron_caseta.markdown @swails
 source/_integrations/mastodon.markdown @fabaff
 source/_integrations/matrix.markdown @tinloaf
 source/_integrations/mcp23017.markdown @jardiamj
+source/_integrations/media_source.markdown @hunterjm
 source/_integrations/mediaroom.markdown @dgomes
 source/_integrations/melcloud.markdown @vilppuvuorinen
 source/_integrations/melissa.markdown @kennedyshead
-source/_integrations/met.markdown @danielhiversen
-source/_integrations/meteo_france.markdown @victorcerutti @oncleben31 @Quentame
+source/_integrations/met.markdown @danielhiversen @thimic
+source/_integrations/meteo_france.markdown @hacf-fr @oncleben31 @Quentame
 source/_integrations/meteoalarm.markdown @rolfberkenbosch
 source/_integrations/metoffice.markdown @MrHarcombe
-source/_integrations/miflora.markdown @danielhiversen @ChristianKuehnel
+source/_integrations/miflora.markdown @danielhiversen @ChristianKuehnel @basnijholt
 source/_integrations/mikrotik.markdown @engrbm87
 source/_integrations/mill.markdown @danielhiversen
 source/_integrations/min_max.markdown @fabaff
@@ -259,17 +271,19 @@ source/_integrations/netdata.markdown @fabaff
 source/_integrations/nexia.markdown @ryannazaretian @bdraco
 source/_integrations/nextbus.markdown @vividboarder
 source/_integrations/nextcloud.markdown @meichthys
+source/_integrations/nightscout.markdown @marciogranzotto
 source/_integrations/nilu.markdown @hfurubotten
 source/_integrations/nissan_leaf.markdown @filcole
 source/_integrations/nmbs.markdown @thibmaek
 source/_integrations/no_ip.markdown @fabaff
+source/_integrations/noaa_tides.markdown @jdelaney72
 source/_integrations/notify.markdown @home-assistant/core
 source/_integrations/notify_events.markdown @matrozov @papajojo
 source/_integrations/notion.markdown @bachya
 source/_integrations/nsw_fuel_station.markdown @nickw444
 source/_integrations/nsw_rural_fire_service_feed.markdown @exxamalte
 source/_integrations/nuheat.markdown @bdraco
-source/_integrations/nuki.markdown @pvizeli
+source/_integrations/nuki.markdown @pschmitt @pvizeli
 source/_integrations/numato.markdown @clssn
 source/_integrations/nut.markdown @bdraco
 source/_integrations/nws.markdown @MatthewFlamm
@@ -284,10 +298,11 @@ source/_integrations/openerz.markdown @misialq
 source/_integrations/opengarage.markdown @danielhiversen
 source/_integrations/opentherm_gw.markdown @mvn23
 source/_integrations/openuv.markdown @bachya
-source/_integrations/openweathermap.markdown @fabaff
+source/_integrations/openweathermap.markdown @fabaff @freekode
 source/_integrations/opnsense.markdown @mtreinish
 source/_integrations/orangepi_gpio.markdown @pascallj
 source/_integrations/oru.markdown @bvlaicu
+source/_integrations/ovo_energy.markdown @timmo001
 source/_integrations/ozw.markdown @cgarwood @marcelveldt @MartinHjelmare
 source/_integrations/panasonic_viera.markdown @joogps
 source/_integrations/panel_custom.markdown @home-assistant/frontend
@@ -306,6 +321,7 @@ source/_integrations/plum_lightpad.markdown @ColinHarrington @prystupa
 source/_integrations/point.markdown @fredrike
 source/_integrations/poolsense.markdown @haemishkyd
 source/_integrations/powerwall.markdown @bdraco @jrester
+source/_integrations/progettihwsw.markdown @ardaseremet
 source/_integrations/prometheus.markdown @knyar
 source/_integrations/proxmoxve.markdown @k4ds3 @jhollowe
 source/_integrations/ps4.markdown @ktnrg45
@@ -327,9 +343,11 @@ source/_integrations/random.markdown @fabaff
 source/_integrations/repetier.markdown @MTrab
 source/_integrations/rfxtrx.markdown @danielhiversen @elupus
 source/_integrations/ring.markdown @balloob
+source/_integrations/risco.markdown @OnFreund
 source/_integrations/rmvtransport.markdown @cgtobi
 source/_integrations/roku.markdown @ctalkington
 source/_integrations/roomba.markdown @pschmitt @cyr-ius @shenxn
+source/_integrations/roon.markdown @pavoni
 source/_integrations/safe_mode.markdown @home-assistant/core
 source/_integrations/saj.markdown @fredericvl
 source/_integrations/salt.markdown @bjornorri
@@ -341,11 +359,13 @@ source/_integrations/script.markdown @home-assistant/core
 source/_integrations/search.markdown @home-assistant/core
 source/_integrations/sense.markdown @kbickar
 source/_integrations/sensibo.markdown @andrey-git
-source/_integrations/sentry.markdown @dcramer
+source/_integrations/sentry.markdown @dcramer @frenck
 source/_integrations/serial.markdown @fabaff
 source/_integrations/seven_segments.markdown @fabaff
 source/_integrations/seventeentrack.markdown @bachya
+source/_integrations/sharkiq.markdown @ajmarks
 source/_integrations/shell_command.markdown @home-assistant/core
+source/_integrations/shelly.markdown @balloob @bieniu
 source/_integrations/shiftr.markdown @fabaff
 source/_integrations/shodan.markdown @fabaff
 source/_integrations/sighthound.markdown @robmarkcole
@@ -353,9 +373,11 @@ source/_integrations/signal_messenger.markdown @bbernhard
 source/_integrations/simplisafe.markdown @bachya
 source/_integrations/sinch.markdown @bendikrb
 source/_integrations/sisyphus.markdown @jkeljo
+source/_integrations/sky_hub.markdown @rogerselwyn
 source/_integrations/slide.markdown @ualex73
 source/_integrations/sma.markdown @kellerza
 source/_integrations/smappee.markdown @bsmappee
+source/_integrations/smart_meter_texas.markdown @grahamwetzler
 source/_integrations/smarthab.markdown @outadoc
 source/_integrations/smartthings.markdown @andrewsayre
 source/_integrations/smarty.markdown @z0mbieprocess
@@ -378,7 +400,7 @@ source/_integrations/starline.markdown @anonym-tsk
 source/_integrations/statistics.markdown @fabaff
 source/_integrations/stiebel_eltron.markdown @fucm
 source/_integrations/stookalert.markdown @fwestenberg
-source/_integrations/stream.markdown @hunterjm
+source/_integrations/stream.markdown @hunterjm @uvjustin
 source/_integrations/stt.markdown @pvizeli
 source/_integrations/suez_water.markdown @ooii
 source/_integrations/sun.markdown @Swamp-Ig
@@ -394,6 +416,7 @@ source/_integrations/synology_dsm.markdown @ProtoThis @Quentame
 source/_integrations/synology_srm.markdown @aerialls
 source/_integrations/syslog.markdown @fabaff
 source/_integrations/tado.markdown @michaelarnauts @bdraco
+source/_integrations/tag.markdown @balloob @dmulcahey
 source/_integrations/tahoma.markdown @philklei
 source/_integrations/tankerkoenig.markdown @guillempages
 source/_integrations/tautulli.markdown @ludeeus
@@ -414,6 +437,7 @@ source/_integrations/tplink.markdown @rytilahti
 source/_integrations/traccar.markdown @ludeeus
 source/_integrations/tradfri.markdown @ggravlingen
 source/_integrations/trafikverket_train.markdown @endor-force
+source/_integrations/trafikverket_weatherstation.markdown @endor-force
 source/_integrations/transmission.markdown @engrbm87 @JPHutchins
 source/_integrations/tts.markdown @pvizeli
 source/_integrations/tuya.markdown @ollo69
@@ -422,7 +446,7 @@ source/_integrations/ubee.markdown @mzdrale
 source/_integrations/unifi.markdown @Kane610
 source/_integrations/unifiled.markdown @florisvdk
 source/_integrations/upb.markdown @gwww
-source/_integrations/upc_connect.markdown @pvizeli
+source/_integrations/upc_connect.markdown @pvizeli @fabaff
 source/_integrations/upcloud.markdown @scop
 source/_integrations/updater.markdown @home-assistant/core
 source/_integrations/upnp.markdown @StevenLooman
@@ -433,31 +457,35 @@ source/_integrations/velbus.markdown @Cereal2nd @brefra
 source/_integrations/velux.markdown @Julius2342
 source/_integrations/vera.markdown @vangorra
 source/_integrations/versasense.markdown @flamm3blemuff1n
-source/_integrations/version.markdown @fabaff
-source/_integrations/vesync.markdown @markperdue @webdjoe
+source/_integrations/version.markdown @fabaff @ludeeus
+source/_integrations/vesync.markdown @markperdue @webdjoe @thegardenmonkey
 source/_integrations/vicare.markdown @oischinger
 source/_integrations/vilfo.markdown @ManneW
 source/_integrations/vivotek.markdown @HarlemSquirrel
 source/_integrations/vizio.markdown @raman325
 source/_integrations/vlc_telnet.markdown @rodripf
+source/_integrations/volkszaehler.markdown @fabaff
+source/_integrations/volumio.markdown @OnFreund
 source/_integrations/waqi.markdown @andrey-git
 source/_integrations/watson_tts.markdown @rutkai
 source/_integrations/weather.markdown @fabaff
 source/_integrations/webostv.markdown @bendavid
 source/_integrations/websocket_api.markdown @home-assistant/core
 source/_integrations/wiffi.markdown @mampfes
+source/_integrations/wilight.markdown @leofig-rj
 source/_integrations/withings.markdown @vangorra
 source/_integrations/wled.markdown @frenck
+source/_integrations/wolflink.markdown @adamkrol93
 source/_integrations/workday.markdown @fabaff
 source/_integrations/worldclock.markdown @fabaff
 source/_integrations/xbox_live.markdown @MartinHjelmare
 source/_integrations/xiaomi_aqara.markdown @danielhiversen @syssi
-source/_integrations/xiaomi_miio.markdown @rytilahti @syssi
+source/_integrations/xiaomi_miio.markdown @rytilahti @syssi @starkillerOG
 source/_integrations/xiaomi_tv.markdown @simse
 source/_integrations/xmpp.markdown @fabaff @flowolf
 source/_integrations/yamaha_musiccast.markdown @jalmeroth
-source/_integrations/yandex_transport.markdown @rishatik92
-source/_integrations/yeelight.markdown @rytilahti @zewelor
+source/_integrations/yandex_transport.markdown @rishatik92 @devbis
+source/_integrations/yeelight.markdown @rytilahti @zewelor @shenxn
 source/_integrations/yeelightsunflower.markdown @lindsaymarkward
 source/_integrations/yessssms.markdown @flowolf
 source/_integrations/yi.markdown @bachya

_config.yml

@@ -100,9 +100,9 @@ social:
 
 # Home Assistant release details
 current_major_version: 0
-current_minor_version: 114
-current_patch_version: 4
-date_released: 2020-08-26
+current_minor_version: 115
+current_patch_version: 1
+date_released: 2020-09-18
 
 # 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/.well-known/security.txt

@@ -0,0 +1,4 @@
+Contact: mailto:security@home-assistant.io
+Preferred-Languages: en
+Canonical: https://www.home-assistant.io/.well-known/security.txt
+Policy: https://www.home-assistant.io/security/

source/_docs/automation/action.markdown

@@ -33,7 +33,7 @@ automation 2:
     notification_service: notify.paulus_iphone
   action:
     # Actions are scripts so can also be a list of actions
-    - service: {{ notification_service }}
+    - service: "{{ notification_service }}"
       data:
         message: Beautiful sunset!
     - delay: 0:35

source/_docs/mqtt/testing.markdown

@@ -10,7 +10,7 @@ The `mosquitto` broker package ships commandline tools (often as `*-clients` pac
 mosquitto_pub -h 127.0.0.1 -t home-assistant/switch/1/on -m "Switch is ON"
 ```
 
-Another way to send MQTT messages by hand is to use the "Developer Tools" in the Frontend. Choose the "MQTT" tab. Enter something similar to the example below into the "Topic" field.
+Another way to send MQTT messages manually is to use the "MQTT" Integration in the frontend. Choose the "Configuration" tab, click "Integrations" and click the "Configure" option under the "MQTT" integration. Enter something similar to the example below into the "topic" field under "Publish a packet*.
 
 ```bash
    home-assistant/switch/1/power

source/_integrations/accuweather.markdown

@@ -9,6 +9,7 @@ ha_config_flow: true
 ha_codeowners:
   - '@bieniu'
 ha_domain: accuweather
+ha_quality_scale: platinum
 ---
 
 The `accuweather` integration uses the [AccuWeather](https://accuweather.com/) web service as a source for weather data for your location.

source/_integrations/airly.markdown

@@ -9,6 +9,7 @@ ha_config_flow: true
 ha_codeowners:
   - '@bieniu'
 ha_domain: airly
+ha_quality_scale: platinum
 ---
 
 The `airly` integration uses the [Airly](https://airly.eu/) web service as a source for air quality data for your location.

source/_integrations/binary_sensor.knx.markdown

@@ -8,21 +8,13 @@ ha_iot_class: Local Push
 ha_domain: knx
 ---
 
-<div class='note'>
-  
-The `knx` integration must be configured correctly to use this integration, see [KNX Integration](/integrations/knx).
-
-</div>
-
 The `knx` sensor platform allows you to monitor [KNX](https://www.knx.org/) binary sensors.
 
 Binary sensors are read-only. To write to the knx-bus configure an exposure [KNX Integration - Expose](/integrations/knx/#exposing-sensor-values-or-time-to-knx-bus).
 
 ## Configuration
 
-The `knx` integration must be configured correctly, see [KNX Integration](/integrations/knx).
-
-To use your binary sensors please add the relevant configuration to your top level KNX configuration key in `configuration.yaml`:
+To use your binary sensors please add the relevant configuration to your top level [KNX Integration](/integrations/knx) configuration key in `configuration.yaml`:
 
 ```yaml
 knx:
@@ -33,7 +25,7 @@ knx:
 
 {% configuration %}
 state_address:
-  description: KNX group address of the binary sensor.
+  description: KNX group address of the binary sensor. *DPT 1*
   required: true
   type: string
 name:
@@ -41,19 +33,14 @@ name:
   required: false
   type: string
 sync_state:
-  description: Actively read the value from the bus. If `False` no GroupValueRead telegrams will be sent to the bus.
+  description: Actively read the value from the bus. If `False` no GroupValueRead telegrams will be sent to the bus. `sync_state` can be set to `init` to just initialize state on startup, `expire <minutes>` to read the state from the KNX bus when no telegram was received for \<minutes\> or `every <minutes>` to update it regularly every \<minutes\>. Maximum value for \<minutes\> is 1440. If just a number is configured "expire"-behaviour is used. Defaults to `True` which is interpreted as "expire 60".
   required: false
-  type: boolean
+  type: [boolean, string, integer]
   default: True
 device_class:
   description: Sets the [class of the device](/integrations/binary_sensor/), changing the device state and icon that is displayed on the frontend.
   required: false
   type: string
-significant_bit:
-  description: Specify which significant bit of the KNX value should be used.
-  required: false
-  type: integer
-  default: 1
 reset_after:
   description: Reset back to OFF state after specified milliseconds.
   required: false

source/_integrations/binary_sensor.template.markdown

@@ -311,33 +311,32 @@ binary_sensor:
   - platform: template
     sensors:
       half_hour:
-        value_template: '{{ (states.sensor.time.state[3:]|int) < 30 }}'
+        value_template: '{{ (states("sensor.time")[3:] | int) < 30 }}'
 ```
 {% endraw %}
 
-An alternative to this is to create an interval-based automation that calls the service `homeassistant.update_entity` for the entities requiring updates. This modified example updates every 2 minutes:
+An alternative to this is to create an interval-based automation that calls the service `homeassistant.update_entity` for the entities requiring updates:
 
 {% raw %}
 ```yaml
 binary_sensor:
 - platform: template
   sensors:
-    minute_is_odd:
-      value_template: '{{ now().minute % 2 }}'
+    half_hour:
+      value_template: '{{ now().minute < 30 }}'
 
 automation:
-  - alias: 'Update minute_is_odd'
+  - alias: 'Update half_hour'
     trigger:
       - platform: time_pattern
-        minutes: '*'
+        minutes: /30
     action:
       - service: homeassistant.update_entity
-        entity_id: binary_sensor.minute_is_odd
+        entity_id: binary_sensor.half_hour
 ```
 {% endraw %}
 
-In the case where the template should be updated every minute, replacing `now()` with `as_local(states.sensor.time.last_changed)`
-can achieve the desired result without the need to create an automation:
+In the case where the template should be updated every minute, just reading `states("sensor.time")` can achieve the desired result without the need to create an automation:
 
 {% raw %}
 ```yaml
@@ -350,6 +349,26 @@ binary_sensor:
 - platform: template
   sensors:
     minute_is_odd:
-      value_template: '{{ as_local(states.sensor.time.last_changed).minute % 2 }}'
+      value_template: >-
+        {% set dummy = states("sensor.time") %}
+        {{ now().minute % 2 == 1 }}
+```
+{% endraw %}
+
+A similar trick of ignoring the sensor value can be used with `states("sensor.date")` for templates that should update at midnight.
+The `time_date` sensors are always true so here we use `and` to ignore the result in a more condensed way:
+
+{% raw %}
+```yaml
+sensor:
+  - platform: time_date
+    display_options:
+      - 'date'
+
+binary_sensor:
+- platform: template
+  sensors:
+    weekend:
+      value_template: {{ states("sensor.date") and now().isoweekday() > 5 }}
 ```
 {% endraw %}

source/_integrations/bond.markdown

@@ -13,6 +13,7 @@ ha_domain: bond
 ha_codeowners:
   - '@prystupa'
 ha_config_flow: true
+ha_quality_scale: platinum
 ---
 
 The Bond integration allows you to control appliances through your [Bond Bridge](https://bondhome.io/). Duplicates your RF remote control.

source/_integrations/broadlink.markdown

@@ -11,6 +11,7 @@ ha_codeowners:
   - '@danielhiversen'
   - '@felipediel'
 ha_domain: broadlink
+ha_config_flow: true
 ---
 
 The Broadlink integration allows you to control and monitor Broadlink universal remotes, smart plugs, power strips, switches and sensors. The following devices are supported:

source/_integrations/calendar.google.markdown

@@ -28,13 +28,12 @@ Generate a Client ID and Client Secret on
 1. Navigate to APIs & Services (left sidebar) > Credentials
 1. Click on the field on the right of the screen, 'CONFIGURE CONSENT SCREEN', select "External" and create.
 1. Set the 'Application Name' (the name of the application asking for consent) to anything you want. We suggest "Home-Assistant".
-1. Scroll to the bottom and save this page. You don't have to fill out anything else here.
-1. Click on the menu item, Credentials, then click 'Create credentials' > OAuth client ID.
+1. You then need to select a `Support email`. To do this, simply click the drop down box and select your email address.
+1. Scroll to the bottom and click `save`. (You don't have to fill out anything else)
+1. You will then be automatically taken to the OAuth consent screen, you don't need to do anything here. Instead, click Credentials in the menu on the left hand side of the screen, then click `+ Create credentials` (at the top of the screen), then select `OAuth client ID`.
 1. Set the Application type to 'Other' (if not present, choose 'TV and Limited Input') and give this credential set a name (like "Home Assistant Credentials") then click 'Create'.
-1. You can now copy the client ID and client secret from the page that follows into a text editor temporarily as you will need to put these in your `configuration.yaml` file.
-1. Click on the menu item, Library, then search for "Google Calendar API" and enable it (if it isn't already enabled automatically through this process).
-1. In order to access your client ID and client secret you can click the navigation menu (hamburger menu) in the top left corner navigate to 'APIs & Services' > Credentials and your credentials will appear under 'OAuth 2.0 Client IDs' with the name you created earlier
-1. Clicking on the name will reveal both the client ID and client secret that you will add to your `configuration.yaml`file below
+1. You will then be presented with a pop-up saying 'OAuth client created' showing `Your Clident ID` and `Your Client Secret`. Make a note of these (for example, copy and paste them into a text editor) as you will need to put these in your `configuration.yaml` file shortly. Once you have noted these strings, click `OK`. If you need to find these credentials again at any point then simply nagivate to `APIs & Services` > `Credentials` and you will see `Home Assistant Credentials` (or whatever you named them in the previous step) under `OAuth 2.0 Clident IDs`. To view both the `Client ID` and `Client secret`, click on the pencil icon, this will take you to the settings page for these credentials and the information will be on the right hand side of the page.
+1. We need to double check that the "Google Calendar API" has been automatically enabled. To do this, select `Library` from the menu, then search for "Google Calendar API". If it is enabled you will see `API Enabled` with a green tick next to it. If it is not enabled, then enable it.
 
 
 If you will later be adding more scopes than just the "Google Calendar API" to the OAuth for this application, you will need to delete your token file under your Home Assistant Profile. You will lose your refresh token due to the re-authenticating to add more API access. It's recommended to use different authorizations for different pieces of Google.

source/_integrations/climate.knx.markdown

@@ -8,15 +8,9 @@ ha_iot_class: Local Push
 ha_domain: knx
 ---
 
-<div class='note'>
-  
-The `knx` integration must be configured correctly to use this integration, see [KNX Integration](/integrations/knx).
-
-</div>
-
 The `knx` climate platform is used as an interface to KNX thermostats and room controllers.
 
-To use your KNX thermostats in your installation, add the following lines to your top level KNX configuration key in `configuration.yaml`:
+To use your KNX thermostats in your installation, add the following lines to your top level [KNX Integration](/integrations/knx) configuration key in `configuration.yaml`:
 
 ```yaml
 # Example configuration.yaml entry
@@ -194,19 +188,19 @@ heat_cool_state_address:
   required: false
   type: string
 operation_mode_frost_protection_address:
-  description: KNX address for switching on/off frost/heat protection mode.
+  description: KNX address for switching on/off frost/heat protection mode. *DPT 1*
   required: false
   type: string
 operation_mode_night_address:
-  description: KNX address for switching on/off night mode.
+  description: KNX address for switching on/off night mode. *DPT 1*
   required: false
   type: string
 operation_mode_comfort_address:
-  description: KNX address for switching on/off comfort mode.
+  description: KNX address for switching on/off comfort mode. *DPT 1*
   required: false
   type: string
 operation_mode_standby_address:
-  description: KNX address for switching on/off standby mode.
+  description: KNX address for switching on/off standby mode. *DPT 1*
   required: false
   type: string  
 operation_modes:
@@ -214,7 +208,7 @@ operation_modes:
   required: false
   type: list
 on_off_address:
-  description: KNX address for switching the climate device on/off.
+  description: KNX address for switching the climate device on/off. *DPT 1*
   required: false
   type: string
 on_off_invert:
@@ -223,7 +217,7 @@ on_off_invert:
   default: false
   type: boolean
 on_off_state_address:
-  description: KNX address for gathering the current state (on/off) of the climate device.
+  description: KNX address for gathering the current state (on/off) of the climate device. *DPT 1*
   required: false
   type: string
 min_temp:

source/_integrations/control4.markdown

@@ -1,10 +1,9 @@
 ---
-title: "Control4"
-description: "Instructions on adding a Control4 system to Home Assistant."
-ha_release: "0.114"
+title: Control4
+description: Instructions on adding a Control4 system to Home Assistant.
+ha_release: '0.114'
 ha_category: Light
-ha_iot_class: "Local Polling"
-ha_quality_scale: silver
+ha_iot_class: Local Polling
 ha_config_flow: true
 ha_codeowners:
   - '@lawtancool'

source/_integrations/cover.knx.markdown

@@ -8,15 +8,9 @@ ha_iot_class: Local Push
 ha_domain: knx
 ---
 
-<div class='note'>
-
-The `knx` integration must be configured correctly to use this integration, see [KNX Integration](/integrations/knx).
-
-</div>
-
 The `knx` cover platform is used as an interface to KNX covers.
 
-To use your KNX covers in your installation, add the following to your `configuration.yaml` file:
+To use your KNX covers in your installation, add the following lines to your top level [KNX Integration](/integrations/knx) configuration key in `configuration.yaml`:
 
 ```yaml
 # Example configuration.yaml entry
@@ -39,31 +33,31 @@ name:
   default: KNX Cover
   type: string
 move_long_address:
-  description: KNX group address for moving the cover full up or down.
+  description: KNX group address for moving the cover full up or down. *DPT 1*
   required: false
   type: string
 move_short_address:
-  description: KNX group address for moving the cover short time up or down.
+  description: KNX group address for moving the cover short time up or down. *DPT 1*
   required: false
   type: string
 stop_address:
-  description: KNX group address for stopping the current movement from the cover.
+  description: KNX group address for stopping the current movement from the cover. *DPT 1*
   required: false
   type: string
 position_address:
-  description: KNX group address for moving the cover to the dedicated position.
+  description: KNX group address for moving the cover to the dedicated position. *DPT 5.001*
   required: false
   type: string
 position_state_address:
-  description: Separate KNX group address for requesting the current position of the cover.
+  description: Separate KNX group address for requesting the current position of the cover. *DPT 5.001*
   required: false
   type: string
 angle_address:
-  description: KNX group address for moving the cover to the dedicated angle.
+  description: KNX group address for moving the cover to the dedicated angle. *DPT 5.001*
   required: false
   type: string
 angle_state_address:
-  description: Separate KNX group address for requesting the current angle of cover.
+  description: Separate KNX group address for requesting the current angle of cover. *DPT 5.001*
   required: false
   type: string
 travelling_time_down:

source/_integrations/default_config.markdown

@@ -14,6 +14,7 @@ This integration is a meta-component and configures a default set of integration
 - [Configuration](/integrations/config/)
 - [Frontend](/integrations/frontend/)
 - [History](/integrations/history/)
+- [Image](/integrations/image/)
 - [Input boolean](/integrations/input_boolean)
 - [Input datetime](/integrations/input_datetime)
 - [Input number](/integrations/input_number)
@@ -21,6 +22,7 @@ This integration is a meta-component and configures a default set of integration
 - [Input text](/integrations/input_text)
 - [Logbook](/integrations/logbook/)
 - [Map](/integrations/map/)
+- [Media Source](/integrations/media_source/)
 - [Mobile App Support](/integrations/mobile_app/)
 - [Person](/integrations/person/)
 - [Scene](/integrations/scene/)
@@ -28,6 +30,7 @@ This integration is a meta-component and configures a default set of integration
 - [Simple Service Discovery Protocol (SSDP)](/integrations/ssdp/)
 - [Sun](/integrations/sun/)
 - [System Health](/integrations/system_health/)
+- [Tag](/integrations/tag/)
 - [Updater](/integrations/updater/)
 - [Zero-configuration networking (zeroconf)](/integrations/zeroconf/)
 - [Zone](/integrations/zone)

source/_integrations/devolo_home_control.markdown

@@ -5,7 +5,7 @@ ha_category:
   - Binary Sensor
   - Climate
   - Cover
-  - Lights
+  - Light
   - Sensor
   - Switch
 ha_release: '0.110'

source/_integrations/doods.markdown

@@ -1,5 +1,5 @@
 ---
-title: DOODS - Distributed Outside Object Detection Service
+title: DOODS - Dedicated Open Object Detection Service
 description: Detect and recognize objects with DOODS.
 ha_category:
   - Image Processing

source/_integrations/dsmr.markdown

@@ -7,6 +7,8 @@ ha_category:
 ha_release: 0.34
 ha_iot_class: Local Push
 ha_domain: dsmr
+ha_codeowners:
+  - '@Robbie1221'
 ---
 
 A sensor platform for Dutch Smart Meters which comply to DSMR (Dutch Smart Meter Requirements), also known as 'Slimme meter' or 'P1 poort'.

source/_integrations/dwd_weather_warnings.markdown

@@ -6,6 +6,10 @@ ha_category:
 ha_release: 0.51
 ha_iot_class: Cloud Polling
 ha_domain: dwd_weather_warnings
+ha_codeowners:
+  - '@runningman84'
+  - '@stephan192'
+  - '@Hummel95'
 ---
 
 The `dwd_weather_warnings` sensor platform uses the [Deutsche Wetter Dienst (DWD)](https://www.dwd.de) as a source for current and advance warnings.

source/_integrations/dynalite.markdown

@@ -358,4 +358,3 @@ Event `dynalite_packet` is fired whenever there is a packet on the Dynalite netw
 | ----------- | --------------------------------------------------------------------------------------------------- |
 | `host`      | Host IP of the Dynalite gateway                                                                     |
 | `packet`    | List of integers representing the 8-byte packet, including the checksum                             |
-

source/_integrations/eafm.md

@@ -15,7 +15,7 @@ The `eafm` integration offers integration with the [UK Environment Agency Flood
 
 ## Configuration
 
-Home Assistant offers the flood monitoring integration through **Configuration** -> **Integrations** -> **UK Environment Ageny - Flood Gauges**.
+Home Assistant offers the flood monitoring integration through **Configuration** -> **Integrations** -> **Environment Agency Flood Gauges**.
 
 You will be prompted to select a monitoring station. You can find the name of nearby monitoring stations on the Flood information service [website](https://flood-warning-information.service.gov.uk/river-and-sea-levels).
 

source/_integrations/elkm1.markdown

@@ -14,6 +14,7 @@ ha_iot_class: Local Push
 ha_domain: elkm1
 ha_config_flow: true
 ha_codeowners:
+  - '@gwww'
   - '@bdraco'
 ---
 

source/_integrations/emulated_kasa.markdown

@@ -4,11 +4,11 @@ description: Instructions on how to integrate Emulated Kasa within Home Assistan
 ha_category:
   - Energy
 ha_iot_class: Local Push
-ha_release: 0.112
-ha_config_flow: false
+ha_release: 0.115
 ha_codeowners:
   - '@kbickar'
 ha_domain: emulated_kasa
+ha_quality_scale: internal
 ---
 
 The Emulated Kasa integration emulates a TP-Link Kasa smart plug and announces the power usage of configured devices to any that might request it on the local network. 

source/_integrations/firmata.markdown

@@ -1,6 +1,6 @@
 ---
 title: Firmata
-description: "Connect Arduino-compatible boards within Home Assistant"
+description: Connect Arduino-compatible boards within Home Assistant
 ha_category:
   - DIY
   - Binary Sensor

source/_integrations/flo.markdown

@@ -1,5 +1,5 @@
 ---
-title: Flo by Moen
+title: Flo
 description: Instructions on how to integrate Flo by Moen into Home Assistant.
 ha_release: 0.115
 ha_category:
@@ -8,7 +8,7 @@ ha_category:
   - Switch
 ha_config_flow: true
 ha_codeowners:
-  - "@dmulcahey"
+  - '@dmulcahey'
 ha_domain: flo
 ---
 

source/_integrations/gios.markdown

@@ -9,6 +9,7 @@ ha_config_flow: true
 ha_codeowners:
   - '@bieniu'
 ha_domain: gios
+ha_quality_scale: platinum
 ---
 
 The `gios` integration uses the [GIOŚ](http://powietrze.gios.gov.pl/pjp/current) web service as a source for air quality data for your location.

source/_integrations/gogogate2.markdown

@@ -1,6 +1,6 @@
 ---
-title: "Gogogate2 and iSmartGate Cover"
-description: "Instructions on how to integrate Gogogate2 and iSmartGate enabled garage door covers into Home Assistant."
+title: Gogogate2 and iSmartGate
+description: Instructions on how to integrate Gogogate2 and iSmartGate enabled garage door covers into Home Assistant.
 logo: gogogate2.png
 ha_category:
   - Cover

source/_integrations/google_assistant.markdown

@@ -77,15 +77,16 @@ If you've added Home Assistant to your phone's home screen, you have to first re
     3. Have the new user go to their `Google Assistant` app to add `[test] your app name` to their account.
 2. If you want to support actively reporting of state to Google's server (configuration option `report_state`) and support `google_assistant.request_sync`, you need to generate a service account.
     1. In the GCP Console, go to the [Create Service account key](https://console.cloud.google.com/apis/credentials/serviceaccountkey) page.
-    2. From the Service account list, select New service account.
-    3. In the Service account name field, enter a name.
-    4. In the Service account ID field, enter an ID.
-    5. From the Role list, select Service Accounts > Service Account Token Creator.
-    6. For the Key type, select the JSON option.
-    7. Click Create. A JSON file that contains your key downloads to your computer.
-    8. Use the information in this file or the file directly to add to the `service_account` key in the configuration.
-    9. Go to the [Google API Console](https://console.cloud.google.com/apis/api/homegraph.googleapis.com/overview).
-    10. Select your project and click Enable HomeGraph API.
+    2. At the top left of the page next to "Google Cloud Platform" logo, select your project created in the Actions on Google console. Confirm this by reviewing the `project_id` and it ensure it matches.
+    3. From the Service account list, select New service account.
+    4. In the Service account name field, enter a name.
+    5. In the Service account ID field, enter an ID.
+    6. From the Role list, select Service Accounts > Service Account Token Creator.
+    7. For the Key type, select the JSON option.
+    8. Click Create. A JSON file that contains your key downloads to your computer.
+    9. Use the information in this file or the file directly to add to the `service_account` key in the configuration.
+    10. Go to the [Google API Console](https://console.cloud.google.com/apis/api/homegraph.googleapis.com/overview).
+    11. Select your project and click Enable HomeGraph API.
 
 
 ### Configuration
@@ -245,11 +246,11 @@ The `request_sync` service requires that the initial sync from Google includes t
 
 The `request_sync` service may fail with a 404 if the `project_id` of the HomeGraph API differs from the `project_id` of the Actions SDK found in the preferences of your project on [Actions on Google console](https://console.actions.google.com). Resolve this by:
 
-  1. Removing your project from the [Actions on Google console](https://console.actions.google.com).
-  2. Add a new project to the [Google Cloud API Console](https://console.cloud.google.com). Here you get a new `project_id`.
-  3. Enable HomeGraph API to the new project.
-  4. Generate a new API key.
-  5. Again, create a new project in the [Actions on Google console](https://console.actions.google.com/). Described above. But at the step 'Build under the Actions SDK box' choose your newly created project. By this, they share the same `project_id`.
+  1. Removing your project from the [Google Cloud API Console](https://console.cloud.google.com).
+  2. Add a new project to the [Actions on Google console](https://console.actions.google.com) Here you get a new `project_id`.
+  3. Run through the previously mentioned [Actions on Google console] setup instructions until the step to create a `service_account`.
+  4. Once you begin to create a new `service_account` in the [Google Cloud API Console], ensure you select the project created in  [Actions on Google console] by verifying the `project_id`.  
+  5. Enable HomeGraph API to the new project.
 
 #### 403 errors on request sync
 

source/_integrations/google_maps.markdown

@@ -12,11 +12,11 @@ The `google_maps` platform allows you to detect presence using the unofficial AP
 
 ## Setup
 
-You first need to create an additional Google account and share your location with that account. This integration will use that account to fetch the location of your device(s). 
+You need two Google accounts. Account A is the account that has to be set up to share its location with account B. Account B is used to fetch the location of your device(s) and will be connected to this integration. 
 
-1. You have to setup sharing through the Google Maps app on your mobile phone. You can find more information [here](https://support.google.com/accounts?p=location_sharing).
-2. You need to use the cookies from that account after you have properly authenticated which you can retrieve with either [Export cookies](https://addons.mozilla.org/en-US/firefox/addon/export-cookies-txt/?src=search) for Firefox (make sure that "Prefix HttpOnly cookies" is unchecked) or [cookies.txt](https://chrome.google.com/webstore/detail/cookiestxt/njabckikapfpffapmjgojcnbfjonfjfg?hl=en-US) for Chrome/Chromium.
-3. Save the cookie file to your Home Assistant configuration directory with the following name: `.google_maps_location_sharing.cookies.` followed by the slugified username of the NEW Google account. Make sure to use the `.com` TLD (e.g., maps.google.com), otherwise the cookie won't be able to provide a valid session.
+1. You first have to setup sharing of the location of account A through the Google Maps app on your mobile phone. Share your location with account B. You can find more information [here](https://support.google.com/accounts?p=location_sharing).
+2. Next, you have to retrieve a valid cookie from Google, while being logged in with account B. Log in with your credentials of account B on [Google Maps](https://www.google.com/maps) with a PC with Firefox or Chrome. Make sure to use the `.com` TLD (e.g., maps.google.com), otherwise the cookie won't be able to provide a valid session. After you have properly authenticated, you can retrieve the cookie with either [Export cookies](https://addons.mozilla.org/en-US/firefox/addon/export-cookies-txt/?src=search) for Firefox (make sure that "Prefix HttpOnly cookies" is unchecked) or [cookies.txt](https://chrome.google.com/webstore/detail/cookiestxt/njabckikapfpffapmjgojcnbfjonfjfg?hl=en-US) for Chrome/Chromium.
+3. Save the cookie file to your Home Assistant configuration directory with the following name: `.google_maps_location_sharing.cookies.` followed by the slugified username of the NEW Google account (account B). 
    - For example: If your email address was `location.tracker@gmail.com`, the filename would be: `.google_maps_location_sharing.cookies.location_tracker_gmail_com`.
 
 ## Configuration

source/_integrations/hlk_sw16.markdown

@@ -9,6 +9,7 @@ ha_iot_class: Local Push
 ha_codeowners:
   - '@jameshilliard'
 ha_domain: hlk_sw16
+ha_config_flow: true
 ---
 
 The [HLK-SW16](http://www.hlktech.net/product_detail.php?ProId=48) by [Hi-Link](http://www.hlktech.net/) is a simple networkable 16 port relay device.

source/_integrations/image.markdown

@@ -4,8 +4,6 @@ description: The image integration handle image assets in Home Assistant.
 ha_category:
   - Other
 ha_release: 0.115
-ha_config_flow: true
-ha_quality_scale: internal
 ha_codeowners:
   - '@home-assistant/core'
 ha_domain: image

source/_integrations/insteon.markdown

@@ -14,6 +14,7 @@ ha_release: 0.39
 ha_domain: insteon
 ha_codeowners:
   - '@teharris1'
+ha_config_flow: true
 ---
 
 This integration adds "local push" support for INSTEON Modems allowing linked INSTEON devices to be used within Home Assistant.

source/_integrations/knx.markdown

@@ -7,6 +7,8 @@ ha_release: 0.24
 ha_iot_class: Local Push
 ha_codeowners:
   - '@Julius2342'
+  - '@farmio'
+  - '@marvin-w'
 ha_domain: knx
 ---
 
@@ -33,7 +35,7 @@ There is currently support for the following device types within Home Assistant:
 - [Weather](/integrations/weather.knx)
 
 
-## Configuration
+## Basic Configuration
 
 To use your KNX bus in your installation, add the following lines to your `configuration.yaml` file:
 
@@ -88,7 +90,7 @@ knx:
 
 {% configuration %}
 host:
-  description: Host of the KNX/IP tunneling device.
+  description: IP address of the KNX/IP tunneling device.
   type: string
   required: true
 port:
@@ -96,7 +98,7 @@ port:
   type: integer
   required: false
 local_ip:
-  description: IP of the local interface.
+  description: IP address of the local interface.
   type: string
   required: false
 {% endconfiguration %}
@@ -111,7 +113,7 @@ knx:
 
 {% configuration %}
 local_ip:
-  description: The local IP address of interface (which should be used for multicasting).
+  description: The local IP address of the interface that shall be used to send multicast packets.
   type: string
   required: true
 {% endconfiguration %}
@@ -139,7 +141,7 @@ state_updater:
   type: boolean
 {% endconfiguration %}
 
-### Services
+## Services
 
 In order to directly interact with the KNX bus, you can use the following service:
 
@@ -154,17 +156,16 @@ address:
   description: KNX group address
   type: string
 payload:
-  description: Payload, either an integer or an array of integers
+  description: Payload to send to the bus. When `type` is not set, raw bytes are sent. Integers are then treated as DPT 1/2/3 payloads. For DPTs > 6 bits send a list. Each value represents 1 octet (0-255). Pad with 0 to DPT byte length.
   type: [integer, list]
 type:
-  description: If set, the payload will not be sent as raw bytes, but encoded as given DPT. KNX sensor types are valid values.
-  required: false
-  type: string
+  description: If set, the payload will not be sent as raw bytes, but encoded as given DPT. KNX sensor types are valid values - see table in [KNX Sensor](/integrations/sensor.knx).
+  type: [string, integer, float]
 {% endconfiguration %}
 
 You can also use the `homeassistant.update_entity` service call to issue GroupValueRead requests for all `*state_address` of a device.
 
-### Exposing entity states, entity attributes or time to KNX bus
+## Exposing entity states, entity attributes or time to KNX bus
 
 KNX integration is able to expose entity states or attributes to KNX bus. The integration will broadcast any change of the exposed value to the KNX bus and answer read requests to the specified group address. It is also possible to expose the current time.
 
@@ -206,13 +207,13 @@ entity_id:
   type: string
   required: false
 attribute:
-  description: Attribute of the entity that shall be sent to the KNX bus. If not set (or `None`) the state will be sent. 
+  description: Attribute of the entity that shall be sent to the KNX bus. If not set (or `None`) the state will be sent.
     Eg. for a light the state is eigther "on" or "off" - with attribute you can expose its "brightness".
   type: string
   required: false
 default:
-  description: Default value to send to the bus if the state or attribute value is `None`. 
-    Eg. a light with state "off" has no brightness attribute so a default value of `0` could be used. 
+  description: Default value to send to the bus if the state or attribute value is `None`.
+    Eg. a light with state "off" has no brightness attribute so a default value of `0` could be used.
     If not set (or `None`) no value would be sent to the bus and a GroupReadRequest to the address would return the last known value.
   type: [boolean, string, integer, float]
   default: None

source/_integrations/kodi.markdown

@@ -7,8 +7,9 @@ ha_category:
 ha_release: pre 0.7
 ha_iot_class: Local Push
 ha_codeowners:
-  - '@armills'
+  - '@OnFreund'
 ha_domain: kodi
+ha_config_flow: true
 ---
 
 The `kodi` platform allows you to control a [Kodi](https://kodi.tv/) multimedia system from Home Assistant.

source/_integrations/light.knx.markdown

@@ -8,12 +8,6 @@ ha_iot_class: Local Push
 ha_domain: knx
 ---
 
-<div class='note'>
-  
-The `knx` integration must be configured correctly to use this integration, see [KNX Integration](/integrations/knx).
-
-</div>
-
 The `knx light` integration is used as an interface to control KNX actuators for lighting applications such as:
 
 - switching actuators
@@ -23,7 +17,7 @@ The `knx light` integration is used as an interface to control KNX actuators for
 
 ## Configuration
 
-To use your KNX light in your installation, add the following lines to your `configuration.yaml` file:
+To use your KNX light in your installation, add the following lines to your top level [KNX Integration](/integrations/knx) configuration key in `configuration.yaml`:
 
 ```yaml
 # Example configuration.yaml entry

source/_integrations/loopenergy.markdown

@@ -6,6 +6,8 @@ ha_category:
 ha_release: 0.17
 ha_iot_class: Cloud Push
 ha_domain: loopenergy
+ha_codeowners:
+  - '@pavoni'
 ---
 
 Integrate your [Loop Energy](https://www.your-loop.com/) meter information into Home Assistant. To use this sensor you need the client serial number and secret keys for your devices.

source/_integrations/media_source.markdown

@@ -4,8 +4,9 @@ description: Instructions on how to access your media with Home Assistant.
 ha_category:
   - Media Source
 ha_release: 0.115
-ha_quality_scale: internal
 ha_domain: media_source
+ha_codeowners:
+  - '@hunterjm'
 ---
 
 The Media Source integration platform allows integrations to expose media for

source/_integrations/met.markdown

@@ -8,6 +8,7 @@ ha_iot_class: Cloud Polling
 ha_config_flow: true
 ha_codeowners:
   - '@danielhiversen'
+  - '@thimic'
 ha_domain: met
 ---
 

source/_integrations/meteo_france.markdown

@@ -7,6 +7,7 @@ ha_category:
   - Sensor
   - Weather
 ha_codeowners:
+  - '@hacf-fr'
   - '@oncleben31'
   - '@Quentame'
 ha_config_flow: true

source/_integrations/miflora.markdown

@@ -8,6 +8,7 @@ ha_iot_class: Local Polling
 ha_codeowners:
   - '@danielhiversen'
   - '@ChristianKuehnel'
+  - '@basnijholt'
 ha_domain: miflora
 ---
 

source/_integrations/netatmo.markdown

@@ -9,10 +9,10 @@ ha_category:
   - Climate
   - Camera
   - Light
-ha_release: "0.20"
+ha_release: '0.20'
 ha_iot_class: Cloud Polling
 ha_codeowners:
-  - "@cgtobi"
+  - '@cgtobi'
 ha_config_flow: true
 ha_domain: netatmo
 ---

source/_integrations/nightscout.markdown

@@ -9,6 +9,7 @@ ha_config_flow: true
 ha_codeowners:
   - '@marciogranzotto'
 ha_domain: nightscout
+ha_quality_scale: platinum
 ---
 
 The Nightscout integration allows you to view your CGM data from [Nightscout](http://www.nightscout.info/) in Home Assistant.

source/_integrations/noaa_tides.markdown

@@ -5,6 +5,8 @@ ha_category:
   - Environment
 ha_release: 0.75
 ha_domain: noaa_tides
+ha_codeowners:
+  - '@jdelaney72'
 ---
 
 The `noaa_tides` sensor platform uses details from [NOAA Tides and Currents](https://tidesandcurrents.noaa.gov/api/) to provide information about the prediction for the tides for any location in the United States.

source/_integrations/notify.knx.markdown

@@ -8,17 +8,11 @@ ha_iot_class: Local Push
 ha_domain: knx
 ---
 
-<div class='note'>
-  
-The `knx` integration must be configured correctly to use this integration, see [KNX Integration](/integrations/knx).
-
-</div>
-
 The `knx` notify platform allows you to send notifications to [KNX](https://www.knx.org/) devices.
 
 ## Configuration
 
-To use your KNX switch in your installation, add the following lines to your `configuration.yaml` file:
+To use your KNX switch in your installation, add the following lines to your top level [KNX Integration](/integrations/knx) configuration key in `configuration.yaml`:
 
 ```yaml
 knx:
@@ -29,7 +23,7 @@ knx:
 
 {% configuration %}
 address:
-  description: KNX group address of the notification.
+  description: KNX group address of the notification. *DPT 16.000*
   required: true
   type: string
 name:

source/_integrations/nuki.markdown

@@ -6,6 +6,7 @@ ha_category:
 ha_release: 0.38
 ha_iot_class: Local Polling
 ha_codeowners:
+  - '@pschmitt'
   - '@pvizeli'
 ha_domain: nuki
 ---

source/_integrations/openweathermap.markdown

@@ -1,5 +1,5 @@
 ---
-title: Openweathermap
+title: OpenWeatherMap
 description: Instructions on how to integrate OpenWeatherMap within Home Assistant.
 ha_release: 0.32
 ha_category:

source/_integrations/ovo_energy.markdown

@@ -8,7 +8,7 @@ ha_release: 0.114
 ha_iot_class: Cloud Polling
 ha_config_flow: true
 ha_codeowners:
-  - "@timmo001"
+  - '@timmo001'
 ha_domain: ovo_energy
 ---
 

source/_integrations/person.markdown

@@ -91,7 +91,14 @@ If you change the YAML, you can reload it by calling the `person.reload` service
 
 ### Customizing the picture for a person
 
-By following the instructions on the [customizing entities](/docs/configuration/customizing-devices#entity_picture) page, you can customize the picture used for a person entity in the `customize:` section of your configuration. For example:
+You can easily upload a picture in the frontend. Simply click on a person, select or drop an image in the input field, and then crop it. 
+
+<div class='videoWrapper'>
+<iframe width="560" height="315" src="https://www.youtube-nocookie.com/embed/rOlRnwaaT7Y" frameborder="0" allowfullscreen></iframe>
+</div>
+
+
+You can also do this using YAML. By following the instructions on the [customizing entities](/docs/configuration/customizing-devices#entity_picture) page, you can customize the picture used for a person entity in the `customize:` section of your configuration. For example:
 
 ```yaml
 customize:

source/_integrations/progettihwsw.markdown

@@ -1,5 +1,5 @@
 ---
-title: ProgettiHWSW
+title: ProgettiHWSW Automation
 description: Instructions on how to integrate the ProgettiHWSW remote relay boards into Home Assistant.
 ha_category:
   - DIY
@@ -8,6 +8,9 @@ ha_category:
 ha_release: 0.115
 ha_iot_class: Local Polling
 ha_domain: progettihwsw
+ha_codeowners:
+  - '@ardaseremet'
+ha_config_flow: true
 ---
 
 The `progettihwsw` integration brings the automation experience with ProgettiHWSW boards to Home Assistant.

source/_integrations/risco.markdown

@@ -1,19 +1,24 @@
 ---
-title: Risco Alarm
+title: Risco
 description: Instructions on how to integrate Risco alarms into HA using Risco Cloud.
 ha_category:
   - Alarm
   - Binary Sensor
-ha_release: "0.115"
+ha_release: '0.115'
 ha_iot_class: Cloud Polling
 ha_config_flow: true
 ha_codeowners:
-  - "@OnFreund"
+  - '@OnFreund'
 ha_domain: risco
+ha_quality_scale: platinum
 ---
 
 This integration connects with Risco Alarms over [Risco Cloud](https://riscocloud.com/).
 
+<div class='note warning'>
+It is recommended to use a regular (non-owner) account with the Risco app/website, and use a different regular account with the integration. Risco has restrictions on concurrent uses by different users, especially if they have different permission levels.
+</div>
+
 ## Configuration
 
 This integration can be configured using the integrations panel in the

source/_integrations/roon.markdown

@@ -1,5 +1,5 @@
 ---
-title: RoonLabs Media Player
+title: RoonLabs music player
 description: Instructions on how to integrate a RoonLabs multi room player into Home Assistant.
 ha_category:
   - Media Player

source/_integrations/scene.knx.markdown

@@ -7,17 +7,11 @@ ha_release: 0.63
 ha_domain: knx
 ---
 
-<div class='note'>
-  
-The `knx` integration must be configured correctly to use this integration, see [KNX Integration](/integrations/knx).
-
-</div>
-
 The `knx` scenes platform allows you to trigger [KNX](https://www.knx.org/) scenes.
 
 ## Configuration
 
-To use your KNX scence in your installation, add the following to your `configuration.yaml` file:
+To use your KNX scence in your installation, add the following lines to your top level [KNX Integration](/integrations/knx) configuration key in `configuration.yaml`:
 
 ```yaml
 # Example configuration.yaml entry
@@ -30,7 +24,7 @@ knx:
 
 {% configuration %}
 address:
-  description: KNX group address for the scene.
+  description: KNX group address for the scene. *DPT 17.001*
   required: true
   type: string
 scene_number:

source/_integrations/script.markdown

@@ -143,11 +143,11 @@ script:
           brightness: 100
       - delay:
           # supports seconds, milliseconds, minutes, hours
-          minutes: {{ minutes }}
+          minutes: "{{ minutes }}"
       - alias: Living room lights on
         service: light.turn_on
         data:
-          entity_id: {{ turn_on_entity }}
+          entity_id: "{{ turn_on_entity }}"
 ```
 
 {% endraw %}

source/_integrations/sensor.knx.markdown

@@ -8,20 +8,14 @@ ha_iot_class: Local Push
 ha_domain: knx
 ---
 
-<div class='note'>
-  
-The `knx` integration must be configured correctly to use this integration, see [KNX Integration](/integrations/knx).
-
-</div>
-
-The `knx` sensor platform allows you to monitor [KNX](https://www.knx.org/) sensors. 
+The `knx` sensor platform allows you to monitor [KNX](https://www.knx.org/) sensors.
 
 Sensors are read-only. To write to the knx-bus configure an exposure [KNX Integration - Expose](/integrations/knx/#exposing-sensor-values-or-time-to-knx-bus).
 
 
 ## Configuration
 
-To use your KNX sensor in your installation, add the following lines to your `configuration.yaml` file:
+To use your KNX sensor in your installation, add the following lines to your top level [KNX Integration](/integrations/knx) configuration key in `configuration.yaml`:
 
 ```yaml
 # Example configuration.yaml entry
@@ -39,7 +33,7 @@ knx:
   sensor:
     - name: Heating.Valve1
       state_address: '2/0/0'
-      sync_state: 30
+      sync_state: expire 30
 ```
 
 {% configuration %}
@@ -52,7 +46,7 @@ name:
   required: false
   type: string
 sync_state:
-  description: Actively read the value from the bus. If `False` no GroupValueRead telegrams will be sent to the bus. You can also define in seconds between 2 and 1440 how often the state update should take place. 
+  description: Actively read the value from the bus. If `False` no GroupValueRead telegrams will be sent to the bus. `sync_state` can be set to `init` to just initialize state on startup, `expire <minutes>` to read the state from the KNX bus when no telegram was received for \<minutes\> or `every <minutes>` to update it regularly every \<minutes\>. Maximum value for \<minutes\> is 1440. If just a number is configured "expire"-behaviour is used. Defaults to `True` which is interpreted as "expire 60".
   required: false
   type: [boolean, string, integer]
   default: True
@@ -210,9 +204,10 @@ knx:
   sensor:
     - name: Heating.Valve1
       state_address: '2/0/0'
+      sync_state: init
       type: 'percent'
     - name: Kitchen.Temperature
       state_address: '6/2/1'
-      sync_state: False
+      sync_state: every 60
       type: 'temperature'
 ```

source/_integrations/sensor.markdown

@@ -27,7 +27,7 @@ The way these sensors are displayed in the frontend can be modified in the [cust
 - **timestamp**: Datetime object or timestamp string.
 - **current**: Current in A.
 - **energy**: Energy in Wh or kWh.
-- **power_factory**: Power Factor in %.
+- **power_factor**: Power Factor in %.
 - **voltage**: Voltage in V.
 
 <p class='img'>

source/_integrations/sharkiq.markdown

@@ -7,7 +7,7 @@ ha_iot_class: Cloud Polling
 ha_release: 0.115
 ha_config_flow: true
 ha_codeowners:
-  - '@amarks'
+  - '@ajmarks'
 ha_domain: sharkiq
 ---
 

source/_integrations/shelly.markdown

@@ -5,20 +5,22 @@ ha_category:
   - Switch
 ha_release: 0.115
 ha_codeowners:
-  - "@balloob"
+  - '@balloob'
+  - '@bieniu'
 ha_domain: shelly
 featured: true
+ha_config_flow: true
 ---
 
 Integrate [Shelly devices](https://shelly.cloud) into Home Assistant.
 
 ## Configuration
 
-To add a Shelly device to your installation, go to **Configuration** >> **Integrations** in the UI. Devices will be automatically discovered when on the same network and listed on the integrations page. Click on "Configure" of the discovered device to add it to Home Assistant.
+To add a Shelly device to your installation, go to **Configuration** >> **Integrations** in the UI, click the + to add a new integration and search for Shelly. Devices will be automatically discovered when on the same network and listed on the integrations page. Click on "Configure" of the discovered device to add it to Home Assistant.
 
 A device can also be added manually, click the button with `+` sign on the integrations page and from the list of integrations, select **Shelly** and follow the instructions shown.
 
 ## Known issues and limitations
 
 - Only supports firmware 1.8 and later
-- Support relays, lights (brightness) and sensors
+- Support relays, lights (with brightness), sensors and rollers

source/_integrations/sky_hub.markdown

@@ -5,6 +5,8 @@ ha_category:
   - Presence Detection
 ha_release: 0.37
 ha_domain: sky_hub
+ha_codeowners:
+  - '@rogerselwyn'
 ---
 
 The `sky_hub` platform offers presence detection by looking at connected devices to a [Sky Hub router](https://www.sky.com/shop/broadband-talk/sky-hub/) based router.

source/_integrations/smappee.markdown

@@ -4,7 +4,7 @@ description: Instructions on how to setup Smappee within Home Assistant.
 ha_category:
   - Hub
   - Energy
-  - Binary sensor
+  - Binary Sensor
   - Sensor
   - Switch
 ha_iot_class: Cloud polling

source/_integrations/smart_meter_texas.markdown

@@ -7,7 +7,7 @@ ha_release: 0.115
 ha_iot_class: Cloud Polling
 ha_config_flow: true
 ha_codeowners:
-  - "@grahamwetzler"
+  - '@grahamwetzler'
 ha_domain: smart_meter_texas
 ---
 

source/_integrations/snips.markdown

@@ -152,8 +152,8 @@ intent_script:
     action:
       - service: light.turn_on
         data:
-          entity_id: light.{{ objectLocation | replace(" ","_") }}
-          color_name: {{ objectColor }}
+          entity_id: 'light.{{ objectLocation | replace(" ","_") }}'
+          color_name: '{{ objectColor }}'
 ```
 {% endraw %}
 

source/_integrations/spider.markdown

@@ -10,6 +10,7 @@ ha_release: 0.75
 ha_codeowners:
   - '@peternijssen'
 ha_domain: spider
+ha_config_flow: true
 ---
 
 The `spider` integration is the main integration to integrate all [Itho Daalderop Spider](https://www.ithodaalderop.nl/spider-thermostaat) related platforms. You will need your Spider account information (username, password) to discover and control devices which are related to your account.

source/_integrations/stream.markdown

@@ -8,6 +8,7 @@ ha_iot_class: Local Push
 ha_quality_scale: internal
 ha_codeowners:
   - '@hunterjm'
+  - '@uvjustin'
 ha_domain: stream
 ---
 

source/_integrations/switch.knx.markdown

@@ -8,17 +8,11 @@ ha_iot_class: Local Push
 ha_domain: knx
 ---
 
-<div class='note'>
-  
-The `knx` integration must be configured correctly to use this integration, see [KNX Integration](/integrations/knx).
-
-</div>
-
 The `knx` switch platform is used as an interface to switching actuators.
 
 ## Configuration
 
-To use your KNX switch in your installation, add the following to your `configuration.yaml` file:
+To use your KNX switch in your installation, add the following lines to your top level [KNX Integration](/integrations/knx) configuration key in `configuration.yaml`:
 
 ```yaml
 knx:
@@ -29,7 +23,7 @@ knx:
 
 {% configuration %}
 address:
-  description: KNX group address for switching the switch on/off.
+  description: KNX group address for switching the switch on/off. *DPT 1*
   required: true
   type: string
 name:
@@ -38,7 +32,7 @@ name:
   default: KNX Switch
   type: string
 state_address:
-  description: Separate KNX group address for retrieving the switch state.
+  description: Separate KNX group address for retrieving the switch state. *DPT 1*
   required: false
   type: string
 {% endconfiguration %}

source/_integrations/tag.markdown

@@ -4,9 +4,9 @@ description: Instructions on how to get started with tags in Home Assistant
 ha_category:
   - Automation
 ha_release: 0.115
-ha_quality_scale: internal
 ha_codeowners:
-  - '@home-assistant/core'
+  - '@balloob'
+  - '@dmulcahey'
 ha_domain: tag
 ---
 

source/_integrations/thethingsnetwork.markdown

@@ -11,7 +11,7 @@ ha_codeowners:
 ha_domain: thethingsnetwork
 ---
 
-The `thethingsnetwork` integration allows one to interact with the [The Things Network](https://www.thethingsnetwork.org). This community-driven and open network supports [LoRaWAN](https://www.lora-alliance.org/) for long range (~5 to 15km) communication with a low bandwidth (51 bytes/message). [Gateways](https://www.thethingsnetwork.org/docs/gateways/) transfers the received data from the sensors to the The Things Network.
+The `thethingsnetwork` integration allows one to interact with the [The Things Network](https://www.thethingsnetwork.org). This community-driven and open network supports [LoRaWAN](https://www.lora-alliance.org/) for long range (~5 to 15 km) communication with a low bandwidth (51 bytes/message). [Gateways](https://www.thethingsnetwork.org/docs/gateways/) transfers the received data from the sensors to the The Things Network.
 
 The Things network support various integrations to make the data available:
 

source/_integrations/trafikverket_weatherstation.markdown

@@ -6,6 +6,8 @@ ha_category:
 ha_release: 0.66
 ha_iot_class: Cloud Polling
 ha_domain: trafikverket_weatherstation
+ha_codeowners:
+  - '@endor-force'
 ---
 
 Showing weather information provided by [Trafikverket](https://www.trafikverket.se/) weather stations in Sweden.

source/_integrations/upc_connect.markdown

@@ -6,6 +6,7 @@ ha_category:
 ha_release: 0.36
 ha_codeowners:
   - '@pvizeli'
+  - '@fabaff'
 ha_domain: upc_connect
 ---
 

source/_integrations/version.markdown

@@ -9,6 +9,7 @@ ha_release: 0.52
 ha_quality_scale: internal
 ha_codeowners:
   - '@fabaff'
+  - '@ludeeus'
 ha_domain: version
 ---
 

source/_integrations/volkszaehler.markdown

@@ -6,6 +6,8 @@ ha_category:
 ha_iot_class: Local Polling
 ha_release: 0.78
 ha_domain: volkszaehler
+ha_codeowners:
+  - '@fabaff'
 ---
 
 The `volkszaehler` sensor platform is consuming the system information provided by the [Volkszaehler](https://wiki.volkszaehler.org/) API.

source/_integrations/weather.knx.markdown

@@ -8,15 +8,9 @@ ha_iot_class: Local Push
 ha_domain: knx
 ---
 
-<div class='note'>
-  
-The `knx` integration must be configured correctly to use this integration, see [KNX Integration](/integrations/knx).
-
-</div>
-
 The `knx` weather platform is used as an interface to KNX weather stations.
 
-To use your KNX weather station in your installation, add the following lines to your top level KNX configuration key in `configuration.yaml`:
+To use your KNX weather station in your installation, add the following lines to your top level [KNX Integration](/integrations/knx) configuration key in `configuration.yaml`:
 
 ```yaml
 # Example configuration.yaml entry

source/_integrations/wilight.markdown

@@ -8,6 +8,7 @@ ha_config_flow: true
 ha_codeowners:
   - '@leofig-rj'
 ha_domain: wilight
+ha_quality_scale: silver
 ---
 
 The `wilight` integration is to integrate [WiLight](http://www.wilight.com.br) devices with Home Assistant.

source/_integrations/wolflink.markdown

@@ -1,5 +1,5 @@
 ---
-title: Wolflink
+title: Wolf SmartSet Service
 description: Instructions on how to integrate Wolf Smart-Set cloud within Home Assistant.
 ha_category:
   - Heating

source/_integrations/xiaomi_miio.markdown

@@ -1,6 +1,6 @@
 ---
-title: "Xiaomi Miio"
-description: "Instructions on how to integrate Xiaomi devices using the Xiaomi Miio integration within Home Assistant."
+title: Xiaomi Miio
+description: Instructions on how to integrate Xiaomi devices using the Xiaomi Miio integration within Home Assistant.
 ha_category:
   - Hub
   - Fan
@@ -15,6 +15,7 @@ ha_release: 0.51
 ha_codeowners:
   - '@rytilahti'
   - '@syssi'
+  - '@starkillerOG'
 ha_domain: xiaomi_miio
 ha_config_flow: true
 ---
@@ -1304,7 +1305,7 @@ Example of `xiaomi_miio.vacuum_clean_segment` use:
 Multiple segments:
 ```yaml
 automation:
-  - alias: Vaccum kitchen and living room
+  - alias: Vacuum kitchen and living room
     trigger:
     - event: start
       platform: homeassistant

source/_lovelace/calendar-card.markdown

@@ -0,0 +1,55 @@
+---
+title: "Calendar Card"
+sidebar_label: Calendar
+description: "The calendar card displays your calendar entities in a month, day and list view"
+---
+
+The Calendar card displays your calendar entities in a month, day and list view.
+
+<p class='img'>
+  <img src='/images/lovelace/lovelace_calendar_card.png' alt='Screenshot of the calendar card'>
+  Screenshot of the calendar card.
+</p>
+
+### Card Settings
+
+{% configuration_basic %}
+Title:
+  description: The title displayed at the top of the card.
+Entities:
+  description: The calendar entities that will be displayed in the card.
+Theme:
+  description: Theme your card using any installed theme in your HA environment.
+{% endconfiguration_basic %}
+
+### YAML
+
+This is for if you use YAML mode or just prefer to use YAML in the Code Editor in the UI.
+
+{% configuration %}
+type:
+  required: true
+  description: calendar
+  type: string
+title:
+  required: false
+  description: The title of the card.
+  type: string
+entities:
+  required: true
+  description: A list of calendar entities that will be displayed in the card.
+  type: list
+theme:
+  required: false
+  description: "Set to any theme within `themes.yaml`"
+  type: string
+{% endconfiguration %}
+
+Example:
+
+```yaml
+type: calendar
+entities:
+  - calendar.calendar_1
+  - calendar.calendar_2
+```

source/_posts/2020-09-18-mac-companion.markdown

@@ -0,0 +1,76 @@
+---
+title: "One more thing…"
+description: "Introducing Home Assistant Companion for macOS."
+date: 2020-09-18 08:00:00
+date_formatted: "September 18, 2020"
+comments: true
+author: Tom Brien
+author_twitter: tbrien88
+categories: Announcements
+og_image: /images/blog/2020-09-18-mac-companion/social.png
+---
+
+Wow, what a birthday week it has been! We've had a [new supervisor release](/blog/2020/09/16/supervisor-joins-the-party), one of the largest and most user-driven core [releases](/blog/2020/09/17/release-115), thanks to the [month of What The Heck?!](/blog/2020/08/18/the-month-of-what-the-heck/). We even got [RFID tags](/blog/2020/09/15/home-assistant-tags) right into the heart of Home Assistant, but we're not done yet! We have "One more thing…"
+
+## Introducing Home Assistant Companion for macOS
+
+Home Assistant Companion is a new application for Mac to control your Home Assistant instance, exposing your Mac sensors to Home Assistant and to receive notifications.
+
+Like many recent updates to the iOS app, we have [@zacwest](https://github.com/zacwest) to thank for this. Zac has ported the iOS app over to Mac and added some great new features specifically for the Mac.
+
+_If you're a Windows user, don't worry, you can integrate your PC with the great [IOT Link](https://iotlink.gitlab.io/index.html) tool._
+
+<p class='img'>
+<img src='/images/blog/2020-09-18-mac-companion/render.png' alt='Rendered image of the Home Assistant Lovelace interface running windowed on a 16-inch Mac Book Pro'></a>
+Home Assistant Companion running on a 16-inch Mac Book Pro
+</p>
+
+## Trigger automations with your Mac
+
+Home Assistant Companion for macOS adds several new binary sensors for your Mac, showing whether it is active and whether a particular microphone or webcam is in use.
+
+Each camera and microphone has its own `binary_sensor` showing whether it is active or not. These can enable some really useful automations, especially for those home working at the moment. You could automatically turn off the radio when answering a call or close the blinds behind you to improve your video quality. To see just how useful this can be in the real world, check out this video of how our very own Frenck is using these sensors in his streaming set up.
+
+<div class="videoWrapper">
+  <iframe width="853" height="480" src="https://www.youtube-nocookie.com/embed/ssRVjqS40-0" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen></iframe>
+</div>
+
+The "active" sensor reports whether the Mac is being actively used. In other words that it is not sleeping, not showing a screensaver, not locked and not just sat idle. You can configure the "Time Until Idle" in one-minute steps from a minimum of 1 minute. You'll find this option in the Sensors section of Preferences.
+
+One huge advantage of running on a Mac compared to a mobile device is the much larger battery. This means we are not constrained by battery-saving measures and can address one of the most common gripes with the iOS app, update intervals. On a Mac, entity updates are immediately triggered when something changes. You will see this reported by the `sensor.DEVICE_NAME_last_update_trigger` reporting `Signaled`.
+
+## Home Assistant Widgets (Big Sur only)
+
+Home Assistant Companion for macOS already supports widgets in Big Sur. Right now, we have an Actions Widget where you can have up to eight actions. You can also create multiple widgets with different sets of actions. If you have an idea for other widgets you'd like to see, pop over to [the community forums and let us know](https://community.home-assistant.io/t/what-kind-of-ios-14-widgets-would-you-like-to-see/211112/14).
+
+<p class='img'>
+<img src='/images/blog/2020-09-18-mac-companion/actions-widget.png' alt='Screenshot of a large Home Assistant Actions widget in Big Sur'></a>
+The large Home Assistant Actions widget in Big Sur.
+</p>
+
+## Interface
+
+The Mac app is definitely a _Mac_ app. The App Configuration page has been removed from Home Assistant's sidebar. Instead, the configuration options and preferences are on the menu bar right where you'd expect to find them for any other app and all the standard shortcuts work too (like `⌘,` for Preferences). You can even open multiple Lovelace windows via File > New.
+
+<p class='img'>
+<img src='/images/blog/2020-09-18-mac-companion/multi_window.png' alt='Screenshot of two Lovelace windows open side-by-side'></a>
+You can have multiple Home Assistant Companion windows open.
+</p>
+
+In the menu bar, you will also find an option to manually send an update to Home Assistant and a new Actions menu where you can see all your [actions](https://companion.home-assistant.io/docs/core/actions) and fire them.
+
+## Notifications
+
+Just like the iOS app, you can send notifications to your Mac with services like `notify.mobile_app_DEVICE_NAME`. One small difference is that [critical notifications](https://companion.home-assistant.io/docs/notifications/critical-notifications) are not yet available for the Mac app. However, all our other notifications features like actionable notifications work on the Mac app. To see what is possible, take a look at [the docs](https://companion.home-assistant.io/).
+
+## Documentation and Support
+
+We are updating the [Companion App docs](https://companion.home-assistant.io) with details for the Mac app. You can also pop over to the [Discord channel](https://discord.com/login?redirect_to=%2Fchannels%2F330944238910963714%2F551871772484698112). If you find a bug or have an idea for a feature, please open up an issue on the [GitHub repository](https://github.com/home-assistant/iOS/issues/new/choose).
+
+## Getting the beta
+
+You can get the beta right now from the `home-assistant/ios` repository: download the `home-assistant-mac.zip` file from the [latest release](https://companion.home-assistant.io/app/mac/latest), unzip and drag it over to your Applications folder. Done!
+
+That's it. All that's left is to wish Home Assistant Happy Birthday one last time and to wait and see what amazing developments the next year brings.
+
+Tom

source/index.html

@@ -77,7 +77,7 @@ description: Open source home automation that puts local control and privacy fir
       <div class="recent-posts material-card text">
         <h1>Recent Blog Posts</h1>
 
-        {% for post in site.posts limit: 3 %}
+        {% for post in site.posts limit: 4 %}
         <li class="post">
           <a href="{{ post.url }}">{{ post.title }}</a>
           <small class="blog-date">{{ post.date_formatted }}</small>

source/lovelace/index.markdown

@@ -7,7 +7,7 @@ redirect_from:
 
 Lovelace is the Home Assistant dashboard. It's a fast, customizable and powerful way for users to manage their homes, working on mobile and desktop.
 
-- 26 different cards to place and configure as you like.
+- 27 different cards to place and configure as you like.
 - Dashboard Editor. Gives you the ability to manage your Lovelace dashboard including a live preview when editing cards.
 - Fast. Using a static configuration allows us to build up the dashboard once.
 - Customizable.
@@ -33,4 +33,4 @@ To try it yourself, check out [the demo](https://demo.home-assistant.io).
 
 * [Awesome HA](https://www.awesome-ha.com/#lovelace-ui)
 * [Community Custom Cards](https://github.com/custom-cards)
-* [Material Design Icons](https://materialdesignicons.com/tag/community)
+* [Material Design Icons](https://materialdesignicons.com/tag/community)