Merge branch 'current' into next

.github/ISSUE_TEMPLATE/feedback.yml

@@ -6,7 +6,7 @@ body:
       value: |
         Thanks for opening an issue to provide feedback on our website/documentation.
 
-        Please note, this form is not for reporting bugs with running Home Assistant or its integrations.
+        **Please note, this form is not for reporting bugs with running Home Assistant or its integrations.**
         Those bugs should be reported in the [Home Assistant Core issue tracker][core].
 
         [core]: https://github.com/home-assistant/core/issues

.github/PULL_REQUEST_TEMPLATE.md

@@ -30,7 +30,7 @@
 
 - Link to parent pull request in the codebase: 
 - Link to parent pull request in the Brands repository: 
-- This PR fixes or closes issue: 
+- This PR fixes or closes issue: fixes #
 
 ## Checklist
 <!--

CODEOWNERS

@@ -14,7 +14,6 @@ source/_integrations/acmeda.markdown @atmurray
 source/_integrations/adax.markdown @danielhiversen
 source/_integrations/adguard.markdown @frenck
 source/_integrations/advantage_air.markdown @Bre77
-source/_integrations/aemet.markdown @noltari
 source/_integrations/agent_dvr.markdown @ispysoftware
 source/_integrations/airly.markdown @bieniu
 source/_integrations/airnow.markdown @asymworks
@@ -32,7 +31,7 @@ source/_integrations/ambiclimate.markdown @danielhiversen
 source/_integrations/ambient_station.markdown @bachya
 source/_integrations/amcrest.markdown @flacjacket
 source/_integrations/analytics.markdown @home-assistant/core @ludeeus
-source/_integrations/androidtv.markdown @JeffLIrion
+source/_integrations/androidtv.markdown @JeffLIrion @ollo69
 source/_integrations/apache_kafka.markdown @bachya
 source/_integrations/api.markdown @home-assistant/core
 source/_integrations/apple_tv.markdown @postlund
@@ -41,6 +40,7 @@ source/_integrations/aprs.markdown @PhilRW
 source/_integrations/arcam_fmj.markdown @elupus
 source/_integrations/arest.markdown @fabaff
 source/_integrations/arris_tg2492lg.markdown @vanbalken
+source/_integrations/aseko_pool_live.markdown @milanmeu
 source/_integrations/asuswrt.markdown @kennedyshead @ollo69
 source/_integrations/atag.markdown @MatsNL
 source/_integrations/aten_pe.markdown @mtdcr
@@ -48,6 +48,7 @@ source/_integrations/atome.markdown @baqs
 source/_integrations/august.markdown @bdraco
 source/_integrations/aurora.markdown @djtimca
 source/_integrations/aurora_abb_powerone.markdown @davet2001
+source/_integrations/aussie_broadband.markdown @nickw444 @Bre77
 source/_integrations/auth.markdown @home-assistant/core
 source/_integrations/automation.markdown @home-assistant/core
 source/_integrations/avea.markdown @pattyland
@@ -97,7 +98,7 @@ source/_integrations/coolmaster.markdown @OnFreund
 source/_integrations/coronavirus.markdown @home-assistant/core
 source/_integrations/counter.markdown @fabaff
 source/_integrations/cover.markdown @home-assistant/core
-source/_integrations/cpuspeed.markdown @fabaff
+source/_integrations/cpuspeed.markdown @fabaff @frenck
 source/_integrations/crownstone.markdown @Crownstone @RicArch97
 source/_integrations/cups.markdown @fabaff
 source/_integrations/daikin.markdown @fredrike
@@ -117,7 +118,8 @@ source/_integrations/dht.markdown @thegardenmonkey
 source/_integrations/digital_ocean.markdown @fabaff
 source/_integrations/discogs.markdown @thibmaek
 source/_integrations/dlna_dmr.markdown @StevenLooman @chishm
-source/_integrations/doorbird.markdown @oblogic7 @bdraco
+source/_integrations/dnsip.markdown @gjohansson-ST
+source/_integrations/doorbird.markdown @oblogic7 @bdraco @flacjacket
 source/_integrations/dsmr.markdown @Robbie1221 @frenck
 source/_integrations/dsmr_reader.markdown @depl0y
 source/_integrations/dunehd.markdown @bieniu
@@ -133,6 +135,7 @@ source/_integrations/egardia.markdown @jeroenterheerdt
 source/_integrations/eight_sleep.markdown @mezz64 @raman325
 source/_integrations/elgato.markdown @frenck
 source/_integrations/elkm1.markdown @gwww @bdraco
+source/_integrations/elmax.markdown @albertogeniola
 source/_integrations/elv.markdown @majuss
 source/_integrations/emby.markdown @mezz64
 source/_integrations/emoncms.markdown @borpin
@@ -166,14 +169,14 @@ source/_integrations/flo.markdown @dmulcahey
 source/_integrations/flock.markdown @fabaff
 source/_integrations/flume.markdown @ChrisMandich @bdraco
 source/_integrations/flunearyou.markdown @bachya
-source/_integrations/flux_led.markdown @icemanch
+source/_integrations/flux_led.markdown @icemanch @bdraco
 source/_integrations/forecast_solar.markdown @klaasnicolaas @frenck
 source/_integrations/forked_daapd.markdown @uvjustin
 source/_integrations/fortios.markdown @kimfrellsen
 source/_integrations/foscam.markdown @skgsergio
 source/_integrations/freebox.markdown @hacf-fr @Quentame
 source/_integrations/freedompro.markdown @stefano055415
-source/_integrations/fritz.markdown @mammuth @AaronDavidSchneider @chemelli74
+source/_integrations/fritz.markdown @mammuth @AaronDavidSchneider @chemelli74 @mib1185
 source/_integrations/fritzbox.markdown @mib1185 @flabbamann
 source/_integrations/fronius.markdown @nielstron @farmio
 source/_integrations/frontend.markdown @home-assistant/frontend
@@ -191,6 +194,7 @@ source/_integrations/gitter.markdown @fabaff
 source/_integrations/glances.markdown @fabaff @engrbm87
 source/_integrations/goalzero.markdown @tkdrob
 source/_integrations/gogogate2.markdown @vangorra @bdraco
+source/_integrations/goodwe.markdown @mletenay @starkillerOG
 source/_integrations/google_assistant.markdown @home-assistant/cloud
 source/_integrations/google_cloud.markdown @lufton
 source/_integrations/gpsd.markdown @fabaff
@@ -217,6 +221,7 @@ source/_integrations/homeassistant.markdown @home-assistant/core
 source/_integrations/homekit.markdown @bdraco
 source/_integrations/homekit_controller.markdown @Jc2k @bdraco
 source/_integrations/homematic.markdown @pvizeli @danielperna84
+source/_integrations/homewizard.markdown @DCSBL
 source/_integrations/honeywell.markdown @rdfurman
 source/_integrations/http.markdown @home-assistant/core
 source/_integrations/huawei_lte.markdown @scop @fphammerle
@@ -236,12 +241,14 @@ 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
+source/_integrations/input_button.markdown @home-assistant/core
 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/intellifire.markdown @jeeftor
 source/_integrations/intesishome.markdown @jnimmo
 source/_integrations/ios.markdown @robbiet480
 source/_integrations/iotawatt.markdown @gtdiehl @jyavenard
@@ -263,12 +270,12 @@ source/_integrations/keyboard_remote.markdown @bendavid @lanrat
 source/_integrations/kmtronic.markdown @dgomes
 source/_integrations/knx.markdown @Julius2342 @farmio @marvin-w
 source/_integrations/kodi.markdown @OnFreund @cgtobi
-source/_integrations/konnected.markdown @heythisisnate @kit-klein
+source/_integrations/konnected.markdown @heythisisnate
 source/_integrations/kostal_plenticore.markdown @stegm
 source/_integrations/kraken.markdown @eifinger
 source/_integrations/kulersky.markdown @emlove
-source/_integrations/lametric.markdown @robbiet480
-source/_integrations/launch_library.markdown @ludeeus
+source/_integrations/lametric.markdown @robbiet480 @frenck
+source/_integrations/launch_library.markdown @ludeeus @DurgNomis-drol
 source/_integrations/lcn.markdown @alengwenus
 source/_integrations/lg_netcast.markdown @Drafteed
 source/_integrations/life360.markdown @pnbruckner
@@ -278,9 +285,9 @@ source/_integrations/litterrobot.markdown @natekspencer
 source/_integrations/local_ip.markdown @issacg
 source/_integrations/logger.markdown @home-assistant/core
 source/_integrations/logi_circle.markdown @evanjd
-source/_integrations/lookin.markdown @ANMalko
+source/_integrations/lookin.markdown @ANMalko @bdraco
 source/_integrations/luci.markdown @mzdrale
-source/_integrations/luftdaten.markdown @fabaff
+source/_integrations/luftdaten.markdown @fabaff @frenck
 source/_integrations/lupusec.markdown @majuss
 source/_integrations/lutron.markdown @JonGilmore
 source/_integrations/lutron_caseta.markdown @swails @bdraco
@@ -305,7 +312,7 @@ source/_integrations/mill.markdown @danielhiversen
 source/_integrations/min_max.markdown @fabaff
 source/_integrations/minecraft_server.markdown @elmurato
 source/_integrations/minio.markdown @tkislan
-source/_integrations/mobile_app.markdown @robbiet480
+source/_integrations/mobile_app.markdown @home-assistant/core
 source/_integrations/modbus.markdown @adamchengtkc @janiversen @vzahradnik
 source/_integrations/modem_callerid.markdown @tkdrob
 source/_integrations/modern_forms.markdown @wonderslug
@@ -337,8 +344,8 @@ source/_integrations/nextcloud.markdown @meichthys
 source/_integrations/nfandroidtv.markdown @tkdrob
 source/_integrations/nightscout.markdown @marciogranzotto
 source/_integrations/nilu.markdown @hfurubotten
+source/_integrations/nina.markdown @DeerMaximum
 source/_integrations/nissan_leaf.markdown @filcole
-source/_integrations/nmap_tracker.markdown @bdraco
 source/_integrations/nmbs.markdown @thibmaek
 source/_integrations/no_ip.markdown @fabaff
 source/_integrations/noaa_tides.markdown @jdelaney72
@@ -359,9 +366,11 @@ source/_integrations/ohmconnect.markdown @robbiet480
 source/_integrations/ombi.markdown @larssont
 source/_integrations/omnilogic.markdown @oliver84 @djtimca @gentoosu
 source/_integrations/onboarding.markdown @home-assistant/core
+source/_integrations/oncue.markdown @bdraco
 source/_integrations/ondilo_ico.markdown @JeromeHXP
 source/_integrations/onewire.markdown @garbled1 @epenet
 source/_integrations/onvif.markdown @hunterjm
+source/_integrations/open_meteo.markdown @frenck
 source/_integrations/openerz.markdown @misialq
 source/_integrations/opengarage.markdown @danielhiversen
 source/_integrations/openhome.markdown @bazwilliams
@@ -371,6 +380,7 @@ source/_integrations/openweathermap.markdown @fabaff @freekode @nzapponi
 source/_integrations/opnsense.markdown @mtreinish
 source/_integrations/orangepi_gpio.markdown @pascallj
 source/_integrations/oru.markdown @bvlaicu
+source/_integrations/overkiz.markdown @imicknl @vlebourl @tetienne
 source/_integrations/ovo_energy.markdown @timmo001
 source/_integrations/ozw.markdown @cgarwood @marcelveldt @MartinHjelmare
 source/_integrations/p1_monitor.markdown @klaasnicolaas
@@ -394,14 +404,13 @@ source/_integrations/profiler.markdown @bdraco
 source/_integrations/progettihwsw.markdown @ardaseremet
 source/_integrations/prometheus.markdown @knyar
 source/_integrations/prosegur.markdown @dgomes
-source/_integrations/proxmoxve.markdown @k4ds3 @jhollowe @Corbeno
+source/_integrations/proxmoxve.markdown @jhollowe @Corbeno
 source/_integrations/ps4.markdown @ktnrg45
 source/_integrations/push.markdown @dgomes
-source/_integrations/pvoutput.markdown @fabaff
+source/_integrations/pvoutput.markdown @fabaff @frenck
 source/_integrations/pvpc_hourly_pricing.markdown @azogue
 source/_integrations/qbittorrent.markdown @geoffreylagaisse
 source/_integrations/qld_bushfire.markdown @exxamalte
-source/_integrations/qnap.markdown @colinodell
 source/_integrations/quantum_gateway.markdown @cisasteelersfan
 source/_integrations/qvr_pro.markdown @oblogic7
 source/_integrations/qwikswitch.markdown @kellerza
@@ -417,7 +426,7 @@ source/_integrations/recollect_waste.markdown @bachya
 source/_integrations/recorder.markdown @home-assistant/core
 source/_integrations/rejseplanen.markdown @DarkFox
 source/_integrations/renault.markdown @epenet
-source/_integrations/repetier.markdown @MTrab
+source/_integrations/repetier.markdown @MTrab @ShadowBr0ther
 source/_integrations/rflink.markdown @javicalle
 source/_integrations/rfxtrx.markdown @danielhiversen @elupus @RobBie1221
 source/_integrations/ridwell.markdown @bachya
@@ -430,6 +439,7 @@ source/_integrations/roomba.markdown @pschmitt @cyr-ius @shenxn
 source/_integrations/roon.markdown @pavoni
 source/_integrations/rpi_gpio_pwm.markdown @soldag
 source/_integrations/rpi_power.markdown @shenxn @swetoast
+source/_integrations/rtsp_to_webrtc.markdown @allenporter
 source/_integrations/ruckus_unleashed.markdown @gabe565
 source/_integrations/safe_mode.markdown @home-assistant/core
 source/_integrations/saj.markdown @fredericvl
@@ -437,12 +447,13 @@ source/_integrations/samsungtv.markdown @escoand @chemelli74
 source/_integrations/scene.markdown @home-assistant/core
 source/_integrations/schluter.markdown @prairieapps
 source/_integrations/scrape.markdown @fabaff
-source/_integrations/screenlogic.markdown @dieselrabbit
+source/_integrations/screenlogic.markdown @dieselrabbit @bdraco
 source/_integrations/script.markdown @home-assistant/core
 source/_integrations/search.markdown @home-assistant/core
 source/_integrations/select.markdown @home-assistant/core
 source/_integrations/sense.markdown @kbickar
-source/_integrations/sensibo.markdown @andrey-git
+source/_integrations/senseme.markdown @mikelawrence @bdraco
+source/_integrations/sensibo.markdown @andrey-git @gjohansson-ST
 source/_integrations/sentry.markdown @dcramer @frenck
 source/_integrations/serial.markdown @fabaff
 source/_integrations/seven_segments.markdown @fabaff
@@ -468,13 +479,14 @@ source/_integrations/smarthab.markdown @outadoc
 source/_integrations/smartthings.markdown @andrewsayre
 source/_integrations/smarttub.markdown @mdz
 source/_integrations/smarty.markdown @z0mbieprocess
+source/_integrations/smhi.markdown @gjohansson-ST
 source/_integrations/sms.markdown @ocalvo
 source/_integrations/smtp.markdown @fabaff
 source/_integrations/solaredge.markdown @frenck
 source/_integrations/solaredge_local.markdown @drobtravels @scheric
 source/_integrations/solarlog.markdown @Ernst79
 source/_integrations/solax.markdown @squishykid
-source/_integrations/soma.markdown @ratsept
+source/_integrations/soma.markdown @ratsept @sebfortier2288
 source/_integrations/somfy.markdown @tetienne
 source/_integrations/sonarr.markdown @ctalkington
 source/_integrations/songpal.markdown @rytilahti @shenxn
@@ -488,7 +500,8 @@ source/_integrations/sql.markdown @dgomes
 source/_integrations/squeezebox.markdown @rajlaud
 source/_integrations/srp_energy.markdown @briglx
 source/_integrations/starline.markdown @anonym-tsk
-source/_integrations/statistics.markdown @fabaff
+source/_integrations/statistics.markdown @fabaff @ThomDietrich
+source/_integrations/steamist.markdown @bdraco
 source/_integrations/stiebel_eltron.markdown @fucm
 source/_integrations/stookalert.markdown @fwestenberg @frenck
 source/_integrations/stream.markdown @hunterjm @uvjustin @allenporter
@@ -509,9 +522,8 @@ source/_integrations/synology_dsm.markdown @hacf-fr @Quentame @mib1185
 source/_integrations/synology_srm.markdown @aerialls
 source/_integrations/syslog.markdown @fabaff
 source/_integrations/system_bridge.markdown @timmo001
-source/_integrations/tado.markdown @michaelarnauts @noltari
+source/_integrations/tado.markdown @michaelarnauts
 source/_integrations/tag.markdown @balloob @dmulcahey
-source/_integrations/tahoma.markdown @philklei
 source/_integrations/tailscale.markdown @frenck
 source/_integrations/tankerkoenig.markdown @guillempages
 source/_integrations/tapsaff.markdown @bazwilliams
@@ -533,14 +545,13 @@ source/_integrations/totalconnect.markdown @austinmroczek
 source/_integrations/tplink.markdown @rytilahti @thegardenmonkey
 source/_integrations/traccar.markdown @ludeeus
 source/_integrations/tractive.markdown @Danielhiversen @zhulik @bieniu
-source/_integrations/trafikverket_train.markdown @endor-force
-source/_integrations/trafikverket_weatherstation.markdown @endor-force
+source/_integrations/trafikverket_train.markdown @endor-force @gjohansson-ST
+source/_integrations/trafikverket_weatherstation.markdown @endor-force @gjohansson-ST
 source/_integrations/transmission.markdown @engrbm87 @JPHutchins
 source/_integrations/tts.markdown @pvizeli
 source/_integrations/tuya.markdown @Tuya @zlinoliver @METISU @frenck
 source/_integrations/twentemilieu.markdown @frenck
-source/_integrations/twinkly.markdown @dr1rrb
-source/_integrations/ubus.markdown @noltari
+source/_integrations/twinkly.markdown @dr1rrb @Robbie1221
 source/_integrations/unifi.markdown @Kane610
 source/_integrations/unifiled.markdown @florisvdk
 source/_integrations/unifiprotect.markdown @briis @AngellusMortis @bdraco
@@ -549,11 +560,11 @@ source/_integrations/upc_connect.markdown @pvizeli @fabaff
 source/_integrations/upcloud.markdown @scop
 source/_integrations/updater.markdown @home-assistant/core
 source/_integrations/upnp.markdown @StevenLooman @ehendrix23
-source/_integrations/uptimerobot.markdown @ludeeus
+source/_integrations/uptimerobot.markdown @ludeeus @chemelli74
 source/_integrations/usb.markdown @bdraco
 source/_integrations/usgs_earthquakes_feed.markdown @exxamalte
 source/_integrations/utility_meter.markdown @dgomes
-source/_integrations/vallox.markdown @andre-richter
+source/_integrations/vallox.markdown @andre-richter @slovdahl @viiru-
 source/_integrations/velbus.markdown @Cereal2nd @brefra
 source/_integrations/velux.markdown @Julius2342
 source/_integrations/venstar.markdown @garbled1
@@ -580,6 +591,7 @@ source/_integrations/webostv.markdown @bendavid @thecode
 source/_integrations/websocket_api.markdown @home-assistant/core
 source/_integrations/wemo.markdown @esev
 source/_integrations/whirlpool.markdown @abmantis
+source/_integrations/whois.markdown @frenck
 source/_integrations/wiffi.markdown @mampfes
 source/_integrations/wilight.markdown @leofig-rj
 source/_integrations/wirelesstag.markdown @sergeymaysak
@@ -597,7 +609,7 @@ source/_integrations/xmpp.markdown @fabaff @flowolf
 source/_integrations/yale_smart_alarm.markdown @gjohansson-ST
 source/_integrations/yamaha_musiccast.markdown @vigonotion @micha91
 source/_integrations/yandex_transport.markdown @rishatik92 @devbis
-source/_integrations/yeelight.markdown @rytilahti @zewelor @shenxn @starkillerOG
+source/_integrations/yeelight.markdown @zewelor @shenxn @starkillerOG
 source/_integrations/yeelightsunflower.markdown @lindsaymarkward
 source/_integrations/yi.markdown @bachya
 source/_integrations/youless.markdown @gjong

Gemfile

@@ -19,7 +19,7 @@ group :jekyll_plugins do
   gem 'jekyll-toc', '0.17.1'
 end
 
-gem 'sinatra', '2.1.0'
+gem 'sinatra', '2.2.0'
 gem 'nokogiri', '1.13.1'
 
 # Windows and JRuby does not include zoneinfo files, so bundle the tzinfo-data gem

Gemfile.lock

@@ -28,7 +28,7 @@ GEM
     ffi (1.15.5-x64-mingw32)
     forwardable-extended (2.6.0)
     http_parser.rb (0.8.0)
-    i18n (1.9.1)
+    i18n (1.10.0)
       concurrent-ruby (~> 1.0)
     jekyll (4.2.1)
       addressable (~> 2.4)
@@ -80,14 +80,14 @@ GEM
     public_suffix (4.0.6)
     racc (1.6.0)
     rack (2.2.3)
-    rack-protection (2.1.0)
+    rack-protection (2.2.0)
       rack
     rake (13.0.6)
-    rb-fsevent (0.11.0)
+    rb-fsevent (0.11.1)
     rb-inotify (0.10.1)
       ffi (~> 1.0)
     rexml (3.2.5)
-    rouge (3.27.0)
+    rouge (3.28.0)
     ruby2_keywords (0.0.5)
     safe_yaml (1.0.5)
     sass (3.4.25)
@@ -97,10 +97,10 @@ GEM
       ffi (~> 1.9)
     sassc (2.1.0-x64-mingw32)
       ffi (~> 1.9)
-    sinatra (2.1.0)
+    sinatra (2.2.0)
       mustermann (~> 1.0)
       rack (~> 2.2)
-      rack-protection (= 2.1.0)
+      rack-protection (= 2.2.0)
       tilt (~> 2.0)
     stringex (2.8.5)
     terminal-table (2.0.0)
@@ -127,7 +127,7 @@ DEPENDENCIES
   rake (= 13.0.6)
   sass-globbing (= 1.1.5)
   sassc (= 2.1.0)
-  sinatra (= 2.1.0)
+  sinatra (= 2.2.0)
   stringex (= 2.8.5)
   tzinfo (~> 2.0)
   tzinfo-data

_config.yml

@@ -105,10 +105,10 @@ social:
     account: home_assistant
 
 # Home Assistant release details
-current_major_version: 2021
-current_minor_version: 12
-current_patch_version: 10
-date_released: 2022-01-17
+current_major_version: 2022
+current_minor_version: 02
+current_patch_version: 9
+date_released: 2022-02-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.

sass/custom/_landingpage.scss

@@ -331,6 +331,10 @@ $ha__primary_color: #03a9f4;
           color: #ffffff;
         }
       }
+      .banner-overlay-button.disabled {
+        background-color: #bdbdbd;
+        cursor: initial;
+       }
       .below-button {
         margin-top: 8px;
         text-align: center;

sass/fontawesome/_path.scss

@@ -11,4 +11,5 @@
 //  src: url('#{$FontAwesomePath}/FontAwesome.otf') format('opentype'); // used when developing fonts
   font-weight: normal;
   font-style: normal;
+  font-display: swap;
 }

source/_data/glossary.yml

@@ -1,9 +1,9 @@
 - topic: Action
   description: "An [Action](/docs/automation/action/) is an event that can be fired as a response to a trigger,  once all conditions have been met."
 - topic: Add-on
-  description: "Add-ons provide additional, standalone, applications that can run beside Home Assistant. Most of these, add-on provided, applications can be integrated into Home Assistant using integrations. Examples of add-ons are: an MQTT broker, database service or a file server."
+  description: "Add-ons are additional standalone third-party software packages that can be installed on Home Assistant OS. Most of these, add-on provided, applications can be integrated into Home Assistant using integrations. Examples of add-ons are: an MQTT broker, database service or a file server."
 - topic: Automation
-  description: "[Automations](/docs/automation/) offer the capability to call a service based on a simple or complex trigger. Automation allows a condition such as a sunset to cause an event, such as a light turning on."
+  description: "[Automations](/docs/automation/) connect one or more triggers to one or more actions in a 'when trigger then do action' fashion with additional optional conditions. For example, an automation might connect the trigger 'sunset' to the action 'turn the lights on' but only if the condition 'someone is home' is met. Pre-made automations for common use-cases are available via [the blueprints feature](/docs/automation/using_blueprints/)."
 - topic: Binary sensor
   description: "A [binary sensor](/integrations/binary_sensor) returns information about things that only have two states - such as on or off."
 - topic: Component
@@ -15,15 +15,15 @@
 - topic: Customize
   description: "[Customization](/docs/configuration/customizing-devices/) allows you to overwrite the default parameters of your devices in the configuration."
 - topic: Device
-  description: "A device is usually a physical unit which can do or observe something."
+  description: "A device is a named collection of entities that all represent the same physical/logical unit, which can do or observe something. An example for a device would be a smart plug named 'Coffee Machine' which provides a `switch` entity plus one or more `sensor` entities for power monitoring or similar."
 - topic: Device tracker
   description: "[Device trackers](/integrations/device_tracker) are used to track the presence, or location, of a device."
 - topic: Discovery
   description: "[Discovery](/integrations/discovery/) is the automatic setup of zeroconf/mDNS and uPnP devices after they are discovered."
 - topic: Domain
-  description: "Entities and services belong to a domain, which is the first part of the entity or service, before the `.`. For example `light.kitchen` is an entity in the `light` domain, while `homeassistant.turn_on` is the `turn_on` service for the `homeassistant` domain."
+  description: "Each integration in Home Assitant has a unique identifier: a domain. All of the entities and services available in Home Assistant are provided by integrations and thus belong to such a domain. The first part of the entity or service, before the `.` shows the domain they belong to. For example `light.kitchen` is an entity in the `light` domain from the [light integration](/integrations/light), while `hue.activate_scene` is the `activate_scene` service for the `hue` domain which belongs to the [Hue integration](/integrations/hue)."
 - topic: Entity
-  description: "An [entity](/docs/configuration/platform_options/) is the representation of a function of a single device, unit, or web service. There may be multiple entities for a single device, unit, or web service, or there may be only one."
+  description: "An entity is the representation of a single control or data point of a device or service inside Home Assistant. A single device or service can thus provide multiple entities to be able to monitor and control all features a device provides. For example, a combined temperature and humidity sensor, in general, provides two `sensor` entities. One for the temperature (e.g., `sensor.temperature` with state `21.0` and unit `°C`) and one for the humity (e.g., `sensor.humidity` with state `65.4` and unit `%`)."
 - topic: Event
   description: "An [event](/docs/configuration/events/) is when something happens."
 - topic: Frontend
@@ -43,7 +43,7 @@
 - topic: Home Assistant Operating System
   description: "Home Assistant OS, the Home Assistant Operating System, is an embedded, minimalistic, operating system designed to run the Home Assistant ecosystem on single board computers (like the Raspberry Pi) or Virtual Machines. The Home Assistant Supervisor can keep it up to date, removing the need for you to manage an operating system."
 - topic: Integration
-  description: "[Integrations](/integrations/) provide the core logic for the functionality in Home Assistant. Like `notify` provides sending notifications."
+  description: "[Integrations](/integrations/) connect and integrates Home Assistant with devices, services, and more. Such an integration contains all the logic that takes care of vendor- and device-specific implementations such as authentication or special protocols and brings those into Home Assistant in a standardized way. For example, the [Hue](/integrations/hue) integration integrates the Philips Hue bridge and its connected bulbs into Home Assistant, making them available as Home Assistant light entities you can control."
 - topic: Lovelace
   description: "[Lovelace](/lovelace/) is the name of the current frontend."
 - topic: Light
@@ -53,7 +53,7 @@
 - topic: Packages
   description: "[Packages](/docs/configuration/packages/) allow you to bundle different component configurations together."
 - topic: Platform
-  description: "[Platforms](/docs/configuration/platform_options/) make the connection to a specific software or hardware platform. For example, the `pushbullet` platform works with the service pushbullet.com to send notifications."
+  description: "[Platforms](/docs/configuration/platform_options/) are building blocks provided by some integrations to be used by other integrations. For example, the [Light](/integrations/light) integration provides the `light platform` that is utilized by all integrations providing `light` entities such as e.g. [Hue](/integrations/hue)."
 - topic: Scene
   description: "[Scenes](/integrations/scene/) capture the states you want certain entities to be. For example, a scene can specify that light A should be turned on and light B should be bright red."
 - topic: Script

source/_docs/automation/trigger.markdown

@@ -715,22 +715,36 @@ automation:
       webhook_id: "some_hook_id"
 ```
 
-You can run this automation by sending an HTTP POST request to `http://your-home-assistant:8123/api/webhook/some_hook_id`. Here is an example using the **curl** command line program, with an empty data payload:
+You can run this automation by sending an HTTP POST request to `http://your-home-assistant:8123/api/webhook/some_hook_id`. Here is an example using the **curl** command line program, with an example data payload:
 
 ```shell
-curl -X POST -d '{ "key": "value"}' https://your-home-assistant:8123/api/webhook/some_hook_id
+curl -X POST -d '{ "key": "value" }' https://your-home-assistant:8123/api/webhook/some_hook_id
 ```
 
-Webhook endpoints don't require authentication, other than knowing a valid webhook ID. You can send a data payload, either as encoded form data or JSON data. The payload is available in an automation template as either `trigger.json` or `trigger.data`. URL query parameters are available in the template as `trigger.query`. Remember to use an HTTPS URL if you've secured your Home Assistant installation with SSL/TLS.
+Webhooks support HTTP POST, PUT, and HEAD requests; POST requests are recommended. HTTP GET requests are not supported.
+
+Remember to use an HTTPS URL if you've secured your Home Assistant installation with SSL/TLS.
 
 Note that a given webhook can only be used in one automation at a time. That is, only one automation trigger can use a specific webhook ID.
 
+### Webhook data
+
+You can send a data payload, either as encoded form data or JSON data. The payload is available in an automation template as either `trigger.json` or `trigger.data`. URL query parameters are available in the template as `trigger.query`.
+
 In order to reference `trigger.json`, the `Content-Type` header must be specified with a value of `application/json`, e.g.:
 
 ```bash
 curl -X POST -H "Content-Type: application/json" https://your-home-assistant:8123/api/webhook/some_hook_id
 ```
 
+### Webhook security
+
+Webhook endpoints don't require authentication, other than knowing a valid webhook ID. Security best practices for webhooks include:
+
+- Do not use webhooks to trigger automations that are destructive, or that can create safety issues. For example, do not use a webhook to unlock a lock, or open a garage door.
+- Treat a webhook ID like a password: use a unique, non-guessable value, and keep it secret.
+- Do not copy-and-paste webhook IDs from public sources, including blueprints. Always create your own.
+
 ## Zone trigger
 
 Zone trigger fires when an entity is entering or leaving the zone. The entity can be either a person, or a device_tracker. For zone automation to work, you need to have setup a device tracker platform that supports reporting GPS coordinates. This includes [GPS Logger](/integrations/gpslogger/), the [OwnTracks platform](/integrations/owntracks/) and the [iCloud platform](/integrations/icloud/).

source/_docs/automation/using_blueprints.markdown

@@ -37,6 +37,27 @@ This will load the blueprint and show a preview in the import dialog. You can ch
 
 The blueprint can now be used for creating automations.
 
+## Keeping blueprints up to date
+
+Blueprints created by the community may go through multiple revisions. Sometimes a user creates a blueprint,
+the community provides feedback, and new functionality is added.
+
+While there's no built-in functionality to update a blueprint you've already imported, you can manually edit
+its YAML content to keep it up to date:
+
+1. Navigate to the blueprints directory (`blueprints/automation/`).
+   The location of this directory depends on the installation method and it's
+   similar to how you find [`configuration.yaml`](/docs/configuration/#editing-configurationyaml).
+1. Next, you must find the blueprint to update. The path name of a blueprint consists of:
+   - The username of the user that created it, which depends from where you imported the blueprint,
+     the forum or GitHub.
+   - The name of the YAML file. For the forum it's the title of the topic in the URL, for GitHub
+     it's the name of the YAML file.
+1. Open the YAML file with your editor and update its contents.
+1. Reload the automations for the changes to take effect.
+
+The new changes will appear to your existing automations as well.
+
 ## Finding new blueprints
 
 The Home Assistant Community forums have a specific tag for blueprints. This tag is used to collect all blueprints.

source/_docs/configuration.markdown

@@ -13,6 +13,13 @@ The easiest option to edit `configuration.yaml` is to use the {% my supervisor_a
 
 If you prefer to use a file editor on your computer, use the {% my supervisor_addon title="Samba add-on" addon="core_samba" %} to access the files as a network share.
 
+The path to your configuration directory can be found in the Home Assistant frontend by going to {% my info title="Configuration -> Settings -> Info" %}
+
+<p class='img'>
+  <img src='/images/screenshots/panel_config_info.png' alt='Screenshot showing the top of the info panel'>
+  Right under the version you are running, you will find what path Home Assistant has loaded the configuration from.
+</div>
+
 _If you use Home Assistant Container, you can find `configuration.yaml` in the config folder that you mounted in your container._
 
 _If you use Home Assistant Operating System, you can find `configuration.yaml` in the `/config` folder of the installation._

source/_docs/configuration/templating.markdown

@@ -369,7 +369,7 @@ Examples using `iif`:
 
 {{ is_state('light.kitchen', 'on') | iif('Yes', 'No') }}
 
-{{ (state('light.kitchen') == 'on') | iif('Yes', 'No') }}
+{{ (states('light.kitchen') == 'on') | iif('Yes', 'No') }}
 ```
 
 {% endraw %}
@@ -508,6 +508,24 @@ The temperature is 25°C
 
 {% endraw %}
 
+### Is defined
+
+Sometimes a template should only return if a value or object is defined, if not, the supplied default value could be returned. This can be useful to validate a JSON payload.
+The `is_defined` filter allows to throw an error if a value or object is not defined.
+
+Example using `is_defined` to parse a JSON payload:
+
+{% raw %}
+
+```text
+{{ value_json.val | is_defined }}
+```
+
+{% endraw %}
+
+This will throw an error `UndefinedError: 'value_json' is undefined` if the JSON payload has no `val` attribute.
+
+
 ### Distance
 
 Not supported in [limited templates](#limited-templates).
@@ -751,8 +769,8 @@ The following overview contains a couple of options to get the needed values:
 # Incoming value:
 {"primes": [2, 3, 5, 7, 11, 13]}
 
-# Extract third prime number
-{{ value_json.primes[2] }}
+# Extract first prime number 
+{{ value_json.primes[0] }}
 
 # Format output
 {{ "%+.1f" | value_json }}

source/_docs/energy/electricity-grid.markdown

@@ -59,6 +59,10 @@ _Attention! Installing CT clamp sensor devices requires opening your electrical
 
 Some energy providers will provide you real-time information about your usage and have this data integrated into Home Assistant.
 
+### Troubleshooting ###
+
+If you are unable to select your energy sensor in the grid consumption drop-down, make sure that its value is being recorded in the Recorder settings.
+
 [Energy integrations](/integrations/#energy)
 
-_Disclaimer: Some links on this page are affiliate links._
+_Disclaimer: Some links on this page are affiliate links helping support the Home Assistant project._

source/_docs/mqtt/discovery.markdown

@@ -340,11 +340,12 @@ A motion detection device which can be represented by a [binary sensor](/integra
 - Configuration topic: `homeassistant/binary_sensor/garden/config`
 - State topic: `homeassistant/binary_sensor/garden/state`
 - Payload:  `{"name": "garden", "device_class": "motion", "state_topic": "homeassistant/binary_sensor/garden/state"}`
+- Retain: The -r switch is added to retain the configuration topic in the broker. Without this, the sensor will not be available after Home Assistant restarts.
 
-To create a new sensor manually. For more details please refer to the [MQTT testing section](/docs/mqtt/testing/).
+To create a new sensor manually.
 
 ```bash
-mosquitto_pub -h 127.0.0.1 -p 1883 -t "homeassistant/binary_sensor/garden/config" -m '{"name": "garden", "device_class": "motion", "state_topic": "homeassistant/binary_sensor/garden/state"}'
+mosquitto_pub -r -h 127.0.0.1 -p 1883 -t "homeassistant/binary_sensor/garden/config" -m '{"name": "garden", "device_class": "motion", "state_topic": "homeassistant/binary_sensor/garden/state"}'
 ```
 
 Update the state.
@@ -359,6 +360,8 @@ Delete the sensor by sending an empty message.
 mosquitto_pub -h 127.0.0.1 -p 1883 -t "homeassistant/binary_sensor/garden/config" -m ''
 ```
 
+For more details please refer to the [MQTT testing section](/docs/mqtt/testing/).
+
 ### Sensors with multiple values
 
 Setting up a sensor with multiple measurement values requires multiple consecutive configuration topic submissions.
@@ -377,9 +380,10 @@ Setting up a switch is similar but requires a `command_topic` as mentioned in th
 - State topic: `homeassistant/switch/irrigation/state`
 - Command topic: `homeassistant/switch/irrigation/set`
 - Payload:  `{"name": "garden", "command_topic": "homeassistant/switch/irrigation/set", "state_topic": "homeassistant/switch/irrigation/state"}`
+- Retain: The -r switch is added to retain the configuration topic in the broker. Without this, the sensor will not be available after Home Assistant restarts.
 
 ```bash
-mosquitto_pub -h 127.0.0.1 -p 1883 -t "homeassistant/switch/irrigation/config" \
+mosquitto_pub -r -h 127.0.0.1 -p 1883 -t "homeassistant/switch/irrigation/config" \
   -m '{"name": "garden", "command_topic": "homeassistant/switch/irrigation/set", "state_topic": "homeassistant/switch/irrigation/state"}'
 ```
 
@@ -455,7 +459,7 @@ Setting up a climate integration (heat only):
 {
   "mode":"off",
   "target_temp":"21.50",
-  "current_temp":"23.60",
+  "current_temp":"23.60"
 }
 ```
 
@@ -479,7 +483,7 @@ Setting up a device tracker:
 - State topic: `homeassistant/device_tracker/paulus/state`
 - Example state payload: `home` or `not_home` or `location name`
 
-If the device supports gps coordinates then they can be sent to Home Assistant by specifying an attributes topic (i.e. "json_attributes_topic") in the configuration payload:
+If the device supports GPS coordinates then they can be sent to Home Assistant by specifying an attributes topic (i.e. "json_attributes_topic") in the configuration payload:
 
 - Attributes topic: `homeassistant/device_tracker/paulus/attributes`
 - Example attributes payload:
@@ -508,5 +512,5 @@ The entity id is automatically generated from the entity's name. All MQTT entity
  }
 ```
 
-In the example above, the the entity_id will be `sensor.device1` instead of `sensor.my_super_device`.
+In the example above, the entity_id will be `sensor.device1` instead of `sensor.my_super_device`.
 

source/_docs/tools/hass.markdown

@@ -8,10 +8,9 @@ The command-line part of Home Assistant is `hass`.
 
 ```bash
 $ hass -h
-usage: hass [-h] [--version] [-c path_to_config_dir] [--safe-mode] [--debug]
-            [--open-ui] [--skip-pip] [-v] [--pid-file path_to_pid_file]
-            [--log-rotate-days LOG_ROTATE_DAYS] [--log-file LOG_FILE]
-            [--log-no-color] [--runner] [--script ...] [--daemon]
+usage: hass [-h] [--version] [-c path_to_config_dir] [--safe-mode]
+            [--debug] [--open-ui] [--skip-pip] [-v] [--log-rotate-days LOG_ROTATE_DAYS] 
+            [--log-file LOG_FILE] [--log-no-color] [--script ...] [--ignore-os-check]
 
 Home Assistant: Observe, Control, Automate.
 
@@ -19,22 +18,18 @@ optional arguments:
   -h, --help            show this help message and exit
   --version             show program's version number and exit
   -c path_to_config_dir, --config path_to_config_dir
-                        Directory that contains the Home Assistant
-                        configuration
+                        Directory that contains the Home Assistant configuration
   --safe-mode           Start Home Assistant in safe mode
   --debug               Start Home Assistant in debug mode
   --open-ui             Open the webinterface in a browser
   --skip-pip            Skips pip install of required packages on startup
   -v, --verbose         Enable verbose logging to file.
-  --pid-file path_to_pid_file
-                        Path to PID file useful for running as daemon
   --log-rotate-days LOG_ROTATE_DAYS
-                        Enables daily log rotation and keeps up to the
-                        specified days
-  --log-file LOG_FILE   Log file to write to. If not set, CONFIG/home-
-                        assistant.log is used
+                        Enables daily log rotation and keeps up to the specified days
+  --log-file LOG_FILE   Log file to write to. If not set, CONFIG/home-assistant.log is used
   --log-no-color        Disable color logs
-  --runner              On restart exit with code 100
   --script ...          Run one of the embedded scripts
-  --daemon              Run Home Assistant as daemon
+  --ignore-os-check     Skips validation of operating system
+
+If restart is requested, exits with code 100
 ```

source/_includes/asides/component_navigation.html

@@ -35,12 +35,16 @@
       {% endif %}
       scores {{page.ha_quality_scale}} on our <a href='/docs/quality_scale/'>quality scale</a>
     {%- endif -%}.
-
-    {% if page.ha_domain %}
-    You can find the source for this integration on <a href='https://github.com/home-assistant/core/tree/dev/homeassistant/components/{{ page.ha_domain }}'>GitHub</a>.
-    {%- endif -%}
   </div>
 
+  {% if page.ha_domain %}
+  <div class='section'>
+    <a href="https://github.com/home-assistant/core/tree/dev/homeassistant/components/{{ page.ha_domain }}" target="_blank"><i class="icon-github"></i> View source on GitHub</a><br />
+    <a href="https://github.com/home-assistant/core/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+{{ page.ha_domain }}%22" target="_blank"><i class="icon-bug"></i> View known issues</a>
+  </div>
+  {%- endif -%}
+
+
   {%- if page.ha_category.first -%}
     <div class='section'>
     <h1 class="title delta">Categories</h1>

source/_includes/common-tasks/data_disk.md

@@ -45,7 +45,7 @@ data_disk: /dev/mmcblk1p4
 ...
 ```
 
-To getting a list of supported detected devices which can be used by `datadisk`:
+To get a list of potential targets which can be used by `datadisk`:
 
 ```sh
 ha os datadisk list

source/_includes/custom/features.html

@@ -110,6 +110,7 @@
       <a
         class="button"
         href="/home-energy-management/"
+        aria-label="Learn more about Home Energy Management"
       >
         LEARN MORE
       </a>

source/_includes/installation/core.md

@@ -33,7 +33,7 @@ sudo apt-get upgrade -y
 Install the dependencies:
 
 ```bash
-sudo apt-get install -y python3 python3-dev python3-venv python3-pip libffi-dev libssl-dev libjpeg-dev zlib1g-dev autoconf build-essential libopenjp2-7 libtiff5 libturbojpeg0 tzdata
+sudo apt-get install -y python3 python3-dev python3-venv python3-pip libffi-dev libssl-dev libjpeg-dev zlib1g-dev autoconf build-essential libopenjp2-7 libtiff5 libturbojpeg0-dev tzdata
 ```
 
 The above-listed dependencies might differ or missing, depending on your system or personal use of Home Assistant.

source/_includes/installation/operating_system.md

@@ -4,7 +4,7 @@
 
 {% if site.installation.types[page.installation_type].board %}
 
-Follow this guide if you want to get started with Home Assistant easily or if you have little to no Linux experience
+Follow this guide if you want to get started with Home Assistant easily or if you have little to no Linux experience.
 
 {% if page.installation_type == 'raspberrypi' %}
 
@@ -57,25 +57,39 @@ This guide assumes that you have a dedicated generic x86 PC (typically an Intel
 
 <b>Summary</b>
 
-You will need to write the HAOS (Home Assistant OS) disk image directly to your boot media, and then configure your x86 to boot from this media, using UEFI boot mode.
+You will need to write the HAOS (Home Assistant OS) disk image directly to your boot media, and configure your x86 to use UEFI boot mode when booting from this media.
 </div>
 
-### Configure the BIOS
+### Configure the BIOS on your x86-64 hardware
 
-To boot Home Assistant OS the BIOS needs to have UEFI boot mode enabled and Secure Boot disabled. The following screenshots are from a 7th generation Intel NUC system. The BIOS menu will likely look different on your systems. However, the options should still be present and named similarly.
+To boot Home Assistant OS, the BIOS needs to have UEFI boot mode enabled and Secure Boot disabled. The following screenshots are from a 7th generation Intel NUC system. The BIOS menu will likely look different on your systems. However, the options should still be present and named similarly.
 
-1. Enter the BIOS using the can enter using the `F2` key (on some systems this might be `Del`, `F1` or `F10`).
+1. To enter the BIOS, start up your x86-64 hardware and repeatedly press the `F2` key (on some systems this might be `Del`, `F1` or `F10`).
 ![Enter BIOS using F2, Del, F1 or F10 key](/images/installation/intel-nuc-enter-bios.jpg)
 
-1. Make sure the UEFI Boot mode is enabled
+1. Make sure the UEFI Boot mode is enabled.
 ![Enable UEFI Boot mode](/images/installation/intel-nuc-uefi-boot.jpg)
 
-1. Disable Secure Boot
+1. Disable Secure Boot.
 ![Disable Secure Boot mode](/images/installation/intel-nuc-disable-secure-boot.jpg)
 
-As a next step, we need to write the Operating System image to the target boot media (Your "boot media" is the disk, SSD, or eMMC that your x86-64 hardware will boot from when it is running Home Assistant). Depending on your system this can be a S-ATA hard disk, S-ATA SSD, a M.2 SSD or even a eMMC. Home Assistant Operating System has no integrated installer. You need to use your Desktop computer (e.g. by using a USB to S-ATA adapter) or boot a live operating system on your target system to install Home Assistant Operating System, by writing the disk image directly onto the boot media for your x86 system.
+1. Save the changes and exit.
 
-If you prefer to use a live operating system, follow the instructions of your Live distribution (e.g., [this Ubuntu guide](https://ubuntu.com/tutorials/try-ubuntu-before-you-install)). Once you booted the live operating system, the following steps on how to write the image to your boot media can be followed.
+- The BIOS configuration is complete.
+
+As a next step, we need to write the Home Assistant Operating System image to the target boot medium. The HAOS has no integrated installer. This means the Operating System is not copied automatically to the internal disk.
+
+- The "boot medium" is the medium your x86-64 hardware will boot from when it is running Home Assistant.
+- Typically, an internal medium is used for the x86-64 hardware. Examples of internal media are S-ATA hard disk, S-ATA SSD, M.2 SSD, or a non-removable eMMC.
+- Alternatively, an external medium can be used to boot HAOS such as a USB SDD (not recommended).
+
+To install the HAOS internally on your x86-64 hardware, there are 2 methods:
+
+1. Copying the HAOS disk image from your Desktop computer onto your boot medium (e.g. by using a USB to S-ATA adapter). This is not an option for a non-removable eMMC on your x86-64 hardware, of course.
+To use this method, follow the steps described in the procedure below: [Write the image to your boot media](#write-the-image-to-your-boot-media).
+2. Copying a live operating system (e.g. Ubuntu) onto a USB device. Then, insert this USB device into your x86-64 hardware and start the Ubuntu.
+
+- To use this method, follow the instructions of your Live distribution (e.g., [this Ubuntu guide](https://ubuntu.com/tutorials/try-ubuntu-before-you-install)). Once you booted the live operating system, follow the steps described in the procedure below: [Write the image to your boot media](#write-the-image-to-your-boot-media).
 
 {% endif %}
 
@@ -134,15 +148,24 @@ _Select and copy the URL or use the "copy" button that appear when you hover it.
 ### Start up your {{site.installation.types[page.installation_type].board}}
 
 {% if page.installation_type == 'generic-x86-64' %}
-1. If you used your Desktop system to write to your boot media, install the boot media ({{site.installation.types[page.installation_type].installation_media}}) into the target system. Otherwise, shutdown the live operating system and make sure to remove the USB flash drive you have been using for the live system.
-2. Make sure an ethernet cable for network is plugged in
+
+1. If you used your desktop system to write the HAOS your boot media, install the boot media ({{site.installation.types[page.installation_type].installation_media}}) in the generic-x86-64 system.
+
+- If you used a live operating system (e.g. Ubuntu), shut down the live operating system and make sure to remove the USB flash drive you used for the live system.
+
+2. Make sure an Ethernet cable is plugged in for network.
 3. Power the system on.
+
+   - Wait for the Home Assistant welcome banner to show up in the console of the generic-x86-64 system.
 {% else %}
-1. Insert the boot media ({{site.installation.types[page.installation_type].installation_media}}) you just created
-2. Attach a ethernet cable for network.
-3. Attach a cable for power
+
+1. Insert the boot media ({{site.installation.types[page.installation_type].installation_media}}) you just created.
+2. Attach an Ethernet cable for network.
+3. Attach the power cable.
 {% endif %}
-4. Within a few minutes you will be able to reach Home Assistant on <a href="http://homeassistant.local:8123" target="_blank">homeassistant.local:8123</a>. If you are running an older Windows version or have a stricter network configuration, you might need to access Home Assistant at <a href="http://homeassistant:8123" target="_blank">homeassistant:8123</a> or `http://X.X.X.X:8123` (replace X.X.X.X with your {{site.installation.types[page.installation_type].board}}’s IP address).
+4. In the browser of your Desktop system, within a few minutes you will be able to reach your new Home Assistant on <a href="http://homeassistant.local:8123" target="_blank">homeassistant.local:8123</a>.
+
+- If you are running an older Windows version or have a stricter network configuration, you might need to access Home Assistant at <a href="http://homeassistant:8123" target="_blank">homeassistant:8123</a> or `http://X.X.X.X:8123` (replace X.X.X.X with your {{site.installation.types[page.installation_type].board}}’s IP address).
 
 {% else %}
 
@@ -167,7 +190,7 @@ Follow this guide if you already are running a supported virtual machine hypervi
 
 ### Create the Virtual Machine
 
-Load the appliance image into your virtual machine hypervisor. (Note: You are free to assign as much resources as you wish to the VM, please assign enough based on your add-on needs)
+Load the appliance image into your virtual machine hypervisor. (Note: You are free to assign as much resources as you wish to the VM, please assign enough based on your add-on needs).
 
 Minimum recommended assignments:
 
@@ -197,7 +220,11 @@ _All these can be extended if your usage calls for more resources._
     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)
 
 {% if page.installation_type == 'windows' or page.installation_type == 'linux' %}
 
@@ -246,7 +273,6 @@ With the Home Assistant Operating System installed and accessible you can contin
 
 {% include getting-started/next_step.html step="Onboarding" link="/getting-started/onboarding/" %}
 
-
 [generic-x86-64]: {{release_url}}/{{site.data.version_data.hassos['ova']}}/haos_generic-x86-64-{{site.data.version_data.hassos['generic-x86-64']}}.img.xz
 [vmdk]: {{release_url}}/{{site.data.version_data.hassos['ova']}}/haos_ova-{{site.data.version_data.hassos['ova']}}.vmdk.zip
 [vhdx]: {{release_url}}/{{site.data.version_data.hassos['ova']}}/haos_ova-{{site.data.version_data.hassos['ova']}}.vhdx.zip

source/_includes/site/header.html

@@ -48,7 +48,7 @@
           <li><a href="/blog/">Blog</a></li>
           <li><a href="/help/">Need help?</a></li>
           <li>
-            <a href="#" class="show-search"><i class="icon-search"></i></a>
+            <a href="#" class="show-search" aria-label="Show search" ><i class="icon-search"></i></a>
           </li>
         </ul>
       </nav>

source/_integrations/advantage_air.markdown

@@ -11,6 +11,7 @@ ha_domain: advantage_air
 ha_quality_scale: platinum
 ha_platforms:
   - binary_sensor
+  - diagnostics
   - climate
   - cover
   - sensor

source/_integrations/aemet.markdown

@@ -7,8 +7,6 @@ ha_category:
   - Sensor
 ha_iot_class: Cloud Polling
 ha_config_flow: true
-ha_codeowners:
-  - '@noltari'
 ha_domain: aemet
 ha_platforms:
   - sensor

source/_integrations/airvisual.markdown

@@ -10,6 +10,7 @@ ha_codeowners:
 ha_domain: airvisual
 ha_config_flow: true
 ha_platforms:
+  - diagnostics
   - sensor
 ---
 

source/_integrations/alarm_control_panel.markdown

@@ -9,4 +9,18 @@ ha_domain: alarm_control_panel
 ---
 
 Home Assistant can give you an interface which is similar to a classic alarm system.
-Please see [manual alarm](/integrations/manual) for alarm configuration.
+Please see [manual alarm](/integrations/manual) or [template alarm](/integrations/alarm_control_panel.template) for alarm configuration.
+
+### Services
+
+Depending on features supported by a specific integration alarm may expose the following services:
+
+| Service | Data | Description |
+| ------- | ---- | ----------- |
+| `alarm_arm_home` | `entity_id` <br> `code` (optional) | Arm the alarm in the home mode.
+| `alarm_arm_away` | `entity_id` <br> `code` (optional) | Arm the alarm in the away mode.
+| `alarm_arm_night` | `entity_id` <br> `code` (optional) | Arm the alarm in the night mode.
+| `alarm_arm_vacation` | `entity_id` <br> `code` (optional) | Arm the alarm in the vacation mode.
+| `alarm_disarm` | `entity_id` <br> `code` (optional) | Disarm the alarm.
+| `alarm_trigger` | `entity_id` <br> `code` (optional) | Trigger the alarm manually.
+| `alarm_arm_custom_bypass` | `entity_id` <br> `code` (optional) | Send arm custom bypass command.

source/_integrations/ambient_station.markdown

@@ -11,6 +11,7 @@ ha_codeowners:
 ha_domain: ambient_station
 ha_platforms:
   - binary_sensor
+  - diagnostics
   - sensor
 ---
 

source/_integrations/aussie_broadband.markdown

@@ -2,17 +2,17 @@
 title: Aussie Broadband
 description: Instructions on how to integrate Aussie Broadband within Home Assistant.
 ha_category:
-- Network
-- Sensor
+  - Network
+  - Sensor
 ha_release: 2022.2
 ha_iot_class: Cloud Polling
 ha_config_flow: true
 ha_codeowners:
-- '@nickw444'
-- '@Bre77'
+  - '@nickw444'
+  - '@Bre77'
 ha_domain: aussie_broadband
 ha_platforms:
-- sensor
+  - sensor
 ---
 
 The Aussie Broadband integration displays various service metrics using the [Aussie Broadband API](https://myaussie-api.aussiebroadband.com.au).

source/_integrations/axis.markdown

@@ -20,6 +20,7 @@ ha_dhcp: true
 ha_platforms:
   - binary_sensor
   - camera
+  - diagnostics
   - light
   - switch
 ---

source/_integrations/bmw_connected_drive.markdown

@@ -51,7 +51,6 @@ The preferred way to enable the `bmw_connected_drive` integration is via **Confi
 | Setting | Description |
 |---------|-------------|
 | Read-only | No execution of services to the vehicle. Still possible to send messages and POIs via `notify` and to request a status update via `bmw_connected_drive.update_state`.
-| Use Home Assistant location for car location polls | Older cars (non i3/i8 build before 7/2014) require the phone to be close to the car to get location updates. Enable this option to use the location of your Home Assistant instance for these queries, so updates are available when your car is in the surrounding of your home. |
 
 The following settings in your `configuration.yaml` file are considered legacy. They will be imported into **Configuration** > **Devices & Services** and you can set the options from above. Changes to `configuration.yaml` after the first import will be ignored.
 
@@ -128,9 +127,9 @@ The `bmw_connected_drive` integration offers several buttons to trigger actions
 
 Using these buttons will impact the state of your vehicle. So use these services with care!
 
-### Air condition
+### Air conditioning
 
-The air condition of the vehicle can be activated with the `button.<your_vehicle>_activate_air_conditioning` button.
+The air conditioning of the vehicle can be activated with the `button.<your_vehicle>_activate_air_conditioning` button.
 
 What exactly is started here depends on the type of vehicle. It might range from just ventilation over auxiliary heating to real air conditioning. If your vehicle is equipped with auxiliary heating, only trigger this service if the vehicle is parked in a location where it is safe to use it (e.g., not in an underground parking or closed garage).
 

source/_integrations/brother.markdown

@@ -12,6 +12,7 @@ ha_domain: brother
 ha_quality_scale: platinum
 ha_zeroconf: true
 ha_platforms:
+  - diagnostics
   - sensor
 ---
 

source/_integrations/climate.mqtt.markdown

@@ -279,11 +279,6 @@ retain:
   required: false
   type: boolean
   default: false
-send_if_off:
-  description: "Set to `false` to suppress sending of all MQTT messages when the current mode is `Off`."
-  required: false
-  type: boolean
-  default: true
 swing_mode_command_template:
   description: A template to render the value sent to the `swing_mode_command_topic` with.
   required: false

source/_integrations/co2signal.markdown

@@ -7,6 +7,7 @@ ha_release: 0.87
 ha_iot_class: Cloud Polling
 ha_domain: co2signal
 ha_platforms:
+  - diagnostics
   - sensor
 ha_config_flow: true
 ---

source/_integrations/coinbase.markdown

@@ -8,6 +8,7 @@ ha_release: 0.61
 ha_iot_class: Cloud Polling
 ha_domain: coinbase
 ha_platforms:
+  - diagnostics
   - sensor
 ha_codeowners:
   - '@tombrien'

source/_integrations/cpuspeed.markdown

@@ -8,9 +8,11 @@ ha_release: pre 0.7
 ha_iot_class: Local Push
 ha_codeowners:
   - '@fabaff'
+  - '@frenck'
 ha_domain: cpuspeed
 ha_config_flow: true
 ha_platforms:
+  - diagnostics
   - sensor
 ---
 

source/_integrations/deconz.markdown

@@ -24,6 +24,7 @@ ha_ssdp: true
 ha_platforms:
   - alarm_control_panel
   - binary_sensor
+  - diagnostics
   - climate
   - cover
   - fan

source/_integrations/default_config.markdown

@@ -20,6 +20,7 @@ This integration is a meta-component and configures a default set of integration
 - [History](/integrations/history/) (`history`)
 - [Image](/integrations/image/) (`image`)
 - [Input boolean](/integrations/input_boolean/) (`input_boolean`)
+- [Input button](/integrations/input_button/) (`input_button`)
 - [Input datetime](/integrations/input_datetime/) (`input_datetime`)
 - [Input number](/integrations/input_number/) (`input_number`)
 - [Input select](/integrations/input_select/) (`input_select`)

source/_integrations/denonavr.markdown

@@ -38,6 +38,7 @@ Known supported devices:
 - Denon AVR-X3200W
 - Denon AVR-X3300W
 - Denon AVR-X3400H
+- Denon AVR-X3500H
 - Denon AVR-X3600H
 - Denon AVR-X3700H
 - Denon AVR-X4100W

source/_integrations/diagnostics.markdown

@@ -0,0 +1,30 @@
+---
+title: Diagnostics
+description: The diagnostics integration can provide integration and device information for debugging purposes.
+ha_category:
+  - Other
+ha_release: 2022.2
+ha_quality_scale: internal
+ha_domain: diagnostics
+---
+
+The diagnostics integration provides a way to download diagnostic data from
+a device or integration, that can be shared in issue reports. Sharing
+diagnostics data when reporting an issue allows developers to diagnose 
+and fix your reported problem quicker.
+
+<p class='img'>
+<img class="no-shadow" src='/images/blog/2022-02/diagnostics.png' alt='Screenshot showing the Download Diagnostics button on a Sonos device page'>
+Screenshot of the Download Diagnostics button on the device page
+</p>
+
+Diagnostics data is provided by an integration, and can be downloaded
+as a text file on the device page, and from the integrations dashboard.
+
+Integrations are required to redact sensitive information from the diagnostics
+data, you can always open the text file and check it, before you send
+it in a public issue.
+
+The diagnostics integration is by default enabled, no action is required to
+enable it. However, not all integrations provide the possibility to download
+diagnostic data.

source/_integrations/dnsip.markdown

@@ -9,6 +9,8 @@ ha_release: '0.40'
 ha_domain: dnsip
 ha_platforms:
   - sensor
+ha_codeowners:
+  - '@gjohansson-ST'
 ---
 
 The DNS IP integration will expose an IP address, fetched via DNS resolution, as its value. It provides both IPv4 and IPv6 lookup as separate sensors depending on accessibility to resolvers.

source/_integrations/doorbird.markdown

@@ -11,11 +11,12 @@ ha_config_flow: true
 ha_codeowners:
   - '@oblogic7'
   - '@bdraco'
+  - '@flacjacket'
 ha_domain: doorbird
 ha_zeroconf: true
 ha_platforms:
-  - button
   - camera
+  - button
 ---
 
 The `doorbird` implementation allows you to integrate your [DoorBird](https://www.doorbird.com/) device in Home Assistant.

source/_integrations/dsmr_reader.markdown

@@ -4,7 +4,7 @@ description: Instructions on how to integrate DSMR Reader.
 ha_category:
   - Energy
   - Sensor
-ha_iot_class: Cloud Polling
+ha_iot_class: Local Push
 ha_release: 0.103
 ha_codeowners:
   - '@depl0y'

source/_integrations/ecobee.markdown

@@ -22,6 +22,8 @@ ha_platforms:
   - notify
   - sensor
   - weather
+ha_zeroconf: true
+ha_homekit: true
 ---
 
 The `ecobee` integration lets you control and view sensor data from [ecobee](https://ecobee.com) thermostats.

source/_integrations/elgato.markdown

@@ -13,6 +13,7 @@ ha_domain: elgato
 ha_zeroconf: true
 ha_platforms:
   - button
+  - diagnostics
   - light
 ---
 

source/_integrations/envisalink.markdown

@@ -5,7 +5,6 @@ ha_category:
   - Alarm
   - Binary Sensor
   - Sensor
-  - Switch
 ha_release: 0.23
 ha_iot_class: Local Push
 ha_domain: envisalink
@@ -13,7 +12,6 @@ ha_platforms:
   - alarm_control_panel
   - binary_sensor
   - sensor
-  - switch
 ---
 
 The `envisalink` integration will allow Home Assistant users who own either a DSC or Honeywell alarm panel to leverage their alarm system and its sensors to provide Home Assistant with rich information about their homes. Connectivity between Home Assistant and the alarm panel is accomplished through a device produced by Eyez On, known as the Envisalink. The Envisalink evl3 and evl4 boards provide a TCP/IP interface to the alarm panel, where it emulates an alarm keypad. This board also exposes a raw TCP/IP based API, upon which this integration is built. Currently, the Envisalink version 4 is the latest model. This integration supports both the evl3 and the evl4.
@@ -25,7 +23,6 @@ There is currently support for the following device types within Home Assistant:
 - Binary Sensor: Reports on zone status (Check the [type/class](/integrations/binary_sensor/#device-class) list for a possible visualization of your zone.)
 - Sensor: Emulates an alphanumeric keypad attached to the alarm panel
 - Alarm Control Panel: Reports on partition status, and can be used to arm/disarm the system
-- Switch: Bypass individual zones. Bypass switches are only available on DSC alarm panels due to limitations in the Honeywell interface.
 
 This is a fully event-based component. Any event sent by the Envisalink device will be immediately reflected within Home Assistant.
 

source/_integrations/esphome.markdown

@@ -16,6 +16,7 @@ ha_platforms:
   - binary_sensor
   - camera
   - button
+  - diagnostics
   - climate
   - cover
   - fan

source/_integrations/evil_genius_labs.markdown

@@ -10,6 +10,7 @@ ha_codeowners:
   - '@balloob'
 ha_domain: evil_genius_labs
 ha_platforms:
+  - diagnostics
   - light
 ---
 

source/_integrations/flunearyou.markdown

@@ -10,6 +10,7 @@ ha_codeowners:
 ha_domain: flunearyou
 ha_config_flow: true
 ha_platforms:
+  - diagnostics
   - sensor
 ---
 

source/_integrations/flux_led.markdown

@@ -15,11 +15,12 @@ ha_platforms:
   - button
   - light
   - number
-  - select
   - sensor
+  - select
   - switch
 ha_codeowners:
   - '@icemanch'
+  - '@bdraco'
 ha_quality_scale: platinum
 ha_config_flow: true
 ha_dhcp: true
@@ -51,6 +52,13 @@ Examples of addressable controllers:
 
 - [Addressable v3](https://www.amazon.com/gp/product/B09BMBSCRF/)
 
+Examples of addressable controllers with strip:
+- [Addressable v1](https://www.amazon.com/gp/product/B07RLF7C86/)
+- [Addressable v2](https://www.amazon.com/gp/product/B07B7CQ2ZB/)
+
+Examples of sockets:
+- [MagicLight Smart Plugs](https://www.magiclightbulbs.com/smart-plugs) or [Amazon](https://www.amazon.com/gp/product/B07XNBVVXV/)
+
 These devices have been sold under at least the following brands:
 
 - Aislan
@@ -131,57 +139,70 @@ This determines the transition between each color.
 
 ### Supported Models
 
-The following models have been tested with integration.
+The following models have been tested.
 
-| Model | Description                 | Notes                           |
-| ----- | --------------------------- | ------------------------------- |
-| 0x01  | Legacy RGB Controller       | Original protocol               |
-| 0x03  | Legacy CCT Controller       | Original protocol               |
-| 0x04  | UFO Controller RGBW         |                                 |
-| 0x06  | Controller RGBW             |                                 |
-| 0x07  | Controller RGBCW            |                                 |
-| 0x08  | Controller RGB with MIC     |                                 |
-| 0x0E  | Floor Lamp RGBCW            |                                 |
-| 0x10  | Christmas Light             |                                 |
-| 0x1A  | Christmas Light             |                                 |
-| 0x1C  | Table Light CCT             |                                 |
-| 0x21  | Bulb Dimmable               |                                 |
-| 0x25  | Controller RGB/WW/CW        | Supports RGB,RGBW,RGBWW,CW,DIM  |
-| 0x33  | Controller RGB              |                                 |
-| 0x35  | Bulb RGBCW                  |                                 |
-| 0x41  | Controller Dimmable         |                                 |
-| 0x44  | Bulb RGBW                   |                                 |
-| 0x52  | Bulb CCT                    |                                 |
-| 0x54  | Downlight RGBW              |                                 |
-| 0x93  | Switch 1c                   |                                 |
-| 0x94  | Switch 1c Watt              |                                 |
-| 0x97  | Socket 1c                   |                                 |
-| 0xA1  | Addressable v1              |                                 |
-| 0xA2  | Addressable v2              |                                 |
-| 0xA3  | Addressable v3              |                                 |
+| Model | Description                 | Microphone | Notes                           |
+| ----- | --------------------------- | ---------- | ------------------------------- |
+| 0x01  | Legacy RGB Controller       | no         | Original protocol               |
+| 0x03  | Legacy CCT Controller       | no         | Original protocol               |
+| 0x04  | UFO Controller RGBW         | no         |                                 |
+| 0x06  | Controller RGBW             | no         |                                 |
+| 0x07  | Controller RGBCW            | no         |                                 |
+| 0x08  | Controller RGB with MIC     | yes        |                                 |
+| 0x09  | Ceiling Light CCT           | no         |                                 |
+| 0x0E  | Floor Lamp RGBCW            | no         |                                 |
+| 0x10  | Christmas Light             | no         |                                 |
+| 0x16  | Magnetic Light CCT          | no         |                                 |
+| 0x17  | Magnetic Light Dimmable     | no         |                                 |
+| 0x1A  | Christmas Light             | no         |                                 |
+| 0x1C  | Table Light CCT             | no         |                                 |
+| 0x1E  | Ceiling Light RGBCW         | no         |                                 |
+| 0x21  | Bulb Dimmable               | no         |                                 |
+| 0x25  | Controller RGB/WW/CW        | no         | Supports RGB, RGBW, RGBWW, CW, DIM |
+| 0x33  | Controller RGB              | no         |                                 |
+| 0x35  | Bulb RGBCW                  | no         |                                 |
+| 0x41  | Controller Dimmable         | no         |                                 |
+| 0x44  | Bulb RGBW                   | no         |                                 |
+| 0x52  | Bulb CCT                    | no         |                                 |
+| 0x54  | Downlight RGBW              | no         |                                 |
+| 0x62  | Controller CCT              | no         |                                 |
+| 0x93  | Switch 1 Channel            | no         |                                 |
+| 0x97  | Socket                      | no         |                                 |
+| 0xA1  | Addressable v1              | no         | Supports UCS1903, SM16703, WS2811, WS2812B, SK6812, INK1003, WS2801, LB1914 |
+| 0xA2  | Addressable v2              | yes        | Supports UCS1903, SM16703, WS2811, WS2811B, SK6812, INK1003, WS2801, WS2815, APA102, TM1914, UCS2904B |
+| 0xA3  | Addressable v3              | yes        | Supports WS2812B, SM16703, SM16704, WS2811, UCS1903, SK6812, SK6812RGBW, INK1003, UCS2904B |
+| 0xA4  | Addressable v4              | no         | Supports WS2812B, SM16703, SM16704, WS2811, UCS1903, SK6812, SK6812RGBW, INK1003, UCS2904B |
+| 0xA6  | Addressable v6              | yes        | Supports WS2812B, SM16703, SM16704, WS2811, UCS1903, SK6812, SK6812RGBW, INK1003, UCS2904B |
+| 0xA7  | Addressable v7              | yes        | Supports WS2812B, SM16703, SM16704, WS2811, UCS1903, SK6812, SK6812RGBW, INK1003, UCS2904B |
+| 0xE1  | Ceiling Light CCT           | no         |                                 |
+| 0xE2  | Ceiling Light Assist        | no         | Auxiliary Switch not supported  |
+
+### Untested Models
+
+The following models have not been tested but may work.
+
+| Model | Description                 | Microphone | Notes                           |
+| ----- | --------------------------- | ---------- | ------------------------------- |
+| 0x02  | Legacy Dimmable Controller  | no         | Original protocol, discontinued |
 
 ### Unsupported Models
 
-The following models have not been tested with integration but may work.
+The following models are confirmed to be unsupported.
 
-| Model | Description                 | Notes                           |
-| ----- | --------------------------- | ------------------------------- |
-| 0x02  | Legacy Dimmable Controller  | Original protocol               |
-| 0x09  | Ceiling Light CCT           |                                 |
-| 0x16  | Magnetic Light CCT          |                                 |
-| 0x17  | Magnetic Light Dimmable     |                                 |
-| 0x19  | Socket 2 USB                |                                 |
-| 0x18  | Plant Light                 |                                 |
-| 0x1B  | Spray Light                 |                                 |
-| 0x1E  | Ceiling Light RGBCW         | Probably works & same as 0x35   |
-| 0x62  | Controller CCT              | May be discontinued             |
-| 0x95  | Switch 2c                   |                                 |
-| 0x96  | Switch 4c                   |                                 |
-| 0xD1  | Digital Light               |                                 |
-| 0xE1  | Ceiling Light               |                                 |
-| 0xE2  | Ceiling Light Assist        |                                 |
-| 0xA4  | Addressable v4              | Probably works & same as 0xA3   |
-| 0xA6  | Addressable v6              | Probably works & same as 0xA3   |
+| Model | Description                 | Microphone | Notes                           |
+| ----- | --------------------------- | ---------- | ------------------------------- |
+| 0x18  | Plant Grow Light            | no         |                                 |
+| 0x19  | Socket with 2 USB           | no         |                                 |
+| 0x1B  | Aroma Fragrance Lamp        | no         |                                 |
+| 0x1D  | Fill Light                  | no         |                                 |
+| 0x94  | Switch 1c Watt              | no         |                                 |
+| 0x95  | Switch 2 Channel            | no         |                                 |
+| 0x96  | Switch 4 Channel            | no         |                                 |
+| 0xD1  | Digital Time Lamp           | no         |                                 |
+
+### Troubleshooting
+
+If a strip controller device will not stay on wifi or goes offline during adjusting colors and effects, upgrading to a power supply with a higher amperage usually resolves any stability issues.
 
 ### Effects
 
@@ -249,7 +270,6 @@ data:
   speed_pct: 80
 ```
 
-
 ### Set Music Mode - Service `flux_led.set_music_mode`
 
 The RGB with MIC (0x08), Addressable v2 (0xA2), and Addressable v3 (0xA3) models have a built-in microphone that have multiple music mode settings.

source/_integrations/fortios.markdown

@@ -1,8 +1,8 @@
 ---
 title: FortiOS
 description: Instructions on how to use Fortinet FortiOS to track devices in Home Assistant.
-ha_category: 
- - Presence Detection
+ha_category:
+  - Presence Detection
 ha_iot_class: Local Polling
 ha_release: 0.97
 ha_domain: fortios

source/_integrations/fritz.markdown

@@ -12,10 +12,12 @@ ha_codeowners:
   - '@mammuth'
   - '@AaronDavidSchneider'
   - '@chemelli74'
+  - '@mib1185'
 ha_iot_class: Local Polling
 ha_platforms:
   - binary_sensor
   - button
+  - diagnostics
   - device_tracker
   - sensor
   - switch

source/_integrations/fritzbox.markdown

@@ -14,6 +14,7 @@ ha_config_flow: true
 ha_ssdp: true
 ha_platforms:
   - binary_sensor
+  - diagnostics
   - climate
   - light
   - sensor

source/_integrations/generic.markdown

@@ -32,7 +32,7 @@ still_image_url:
   required: false
   type: string
 stream_source:
-  description: "The URL your camera serves the live stream on, e.g., `rtsp://user:pass@192.168.1.21:554/`. Can be a [template](/topics/templating/). Usernames and passwords must be embedded in the URL. At least one of still_image_url or stream_source must be provided."
+  description: "The URL your camera serves the live stream on, e.g., `rtsp://user:pass@192.168.1.21:554/`. Can be a [template](/topics/templating/). Usernames and passwords must be embedded in the URL. At least one of still_image_url or stream_source must be provided. Note that a stream_source without a still_image_url can only be used if the [stream integration](/integrations/stream/) is configured."
   required: false
   type: string
 name:

source/_integrations/github.markdown

@@ -8,6 +8,7 @@ ha_release: 0.88
 ha_iot_class: Cloud Polling
 ha_domain: github
 ha_platforms:
+  - diagnostics
   - sensor
 ha_codeowners:
   - '@timmo001'

source/_integrations/goodwe.markdown

@@ -1,5 +1,5 @@
 ---
-title: GoodWe
+title: GoodWe Inverter
 description: Instructions on how to connect your GoodWe Inverter to Home Assistant.
 ha_category:
   - Sensor
@@ -8,10 +8,13 @@ ha_iot_class: Local Polling
 ha_config_flow: true
 ha_release: 2022.2
 ha_codeowners:
-  - "@mletenay"
+  - '@mletenay'
+  - '@starkillerOG'
 ha_domain: goodwe
 ha_platforms:
+  - number
   - sensor
+  - select
 ---
 
 The GoodWe integration will poll a [GoodWe](http://www.goodwe.com/) solar inverter over the local network and present its runtime values as sensors in Home Assistant.

source/_integrations/google_assistant.markdown

@@ -109,16 +109,28 @@ If you want to support active reporting of state to Google's server (configurati
 
 ### Enable Local Fulfillment
 
+<div class='note'>
+
+The [`ssl_certificate` option](/integrations/http/#ssl_certificate) in the `http` integration must not have a value or this feature won't work.
+
+This is because Google requires a valid certificate and the way it connects to Home Assistant for local fulfillment makes that impossible. Consider using a reverse proxy such as the {% my supervisor_addon addon="core_nginx_proxy" title="NGINX SSL" %} add-on instead of directing external traffic directly to Home Assistant.
+
+</div>
+
 1. Open the project you created in the [Actions on Google console](https://console.actions.google.com/).
 2. Click `Develop` on the top of the page, then click `Actions` located in the hamburger menu on the top left.
 3. Upload [this Javascript file](/assets/integrations/google_assistant/app.js) for both Node and Chrome by clicking the `Upload Javascript files` button.
 4. Add device scan configuration:
-  1. Click `+ New scan config`
-  2. Select `MDNS`
-  3. set mDNS service name to `_home-assistant._tcp.local`
-5. `Save` your changes.
-6. Either wait for 30 minutes, or restart your connected Google device.
-7. Restart Home Assistant Core.
+   1. Click `+ New scan config`
+   2. Select `MDNS`
+   3. Set mDNS service name to `_home-assistant._tcp.local`
+   4. Click `Add field`, then under `Select a field` select `name`
+   5. Enter a new `value` field set to `.*\._home-assistant\._tcp\.local`
+5. Check the box `Support local query` under `Add capabilities`.
+6. `Save` your changes.
+7. Either wait for 30 minutes, or restart your connected Google device.
+8. Restart Home Assistant Core.
+9. With a Google Assistant device, try saying "OK Google, sync my devices." This can be helpful to avoid issues, especially if you are enabling local fulfillment sometime after adding cloud Google Assistant support.
 
 You can debug the setup by following [these instructions](https://developers.google.com/assistant/smarthome/develop/local#debugging_from_chrome)
 

source/_integrations/gtfs.markdown

@@ -62,7 +62,7 @@ name:
   default: GTFS Sensor
   type: string
 offset:
-  description: A minimum delay to look for. If a departure is in less time than `offset`, it will be ignored.
+  description: "A minimum delay to look for. If a departure is in less time than `offset`, it will be ignored. Set the value either in seconds (`integer`), or using one of these `time` formats: `offset: 'HH:MM:SS'`, `offset: 'HH:MM'`. "
   required: false
   default: 0
   type: [integer, time]

source/_integrations/guardian.markdown

@@ -14,6 +14,7 @@ ha_domain: guardian
 ha_zeroconf: true
 ha_platforms:
   - binary_sensor
+  - diagnostics
   - sensor
   - switch
 ha_dhcp: true

source/_integrations/harmony.markdown

@@ -32,6 +32,8 @@ Supported units:
 
 {% include integrations/config_flow.md %}
 
+**Note:** Depending on the firmware, you may need to enable XMPP for this integration to work. From your Harmony app, go to: **Menu** > **Harmony Setup** > **Add/Edit Devices & Activities** > **Remote & Hub** > **Enable XMPP**.
+
 Once the Logitech Harmony Hub has been configured, the default activity and duration in seconds between sending commands to a device can be adjusted in the settings via **Configuration** >> **Devices & Services** >> **Your Logitech Harmony Hub**
 
 ### Configuration file

source/_integrations/homekit.markdown

@@ -460,6 +460,25 @@ automation:
     packet: XXXXXXXX
 ```
 
+## Events
+
+The HomeKit integration emits `homekit_state_change` events. These events can be used in automations to know when an entity's state was changed from HomeKit.
+
+```yaml
+# Example for handling a HomeKit event
+automation:
+  trigger:
+    - platform: event
+      event_type: homekit_state_change
+      event_data:
+        entity_id: cover.garage_door
+        service: open_cover
+  action:
+    - service: persistent_notification.create
+      data:
+        message: "The garage door got opened via HomeKit"
+```
+
 ## Troubleshooting
 
 ### All or some devices are intermittently unresponsive

source/_integrations/homekit_controller.markdown

@@ -27,6 +27,7 @@ ha_platforms:
   - binary_sensor
   - camera
   - button
+  - diagnostics
   - climate
   - cover
   - fan

source/_integrations/homewizard.markdown

@@ -10,7 +10,9 @@ ha_domain: homewizard
 ha_codeowners:
   - '@DCSBL'
 ha_platforms:
+  - diagnostics
   - sensor
+  - switch
 ha_zeroconf: true
 ---
 

source/_integrations/html5.markdown

@@ -91,15 +91,13 @@ The `html5` platform can only function if all of the following requirements are
 
 ### Configuring the platform
 
-1. Make sure you can access your Home Assistant installation from outside your network over HTTPS ([see documentation](/docs/configuration/remote/)) or can perform an alternative [Domain Name Verification Method](https://support.google.com/webmasters/answer/9008080#domain_name_verification) on the domain used by Home Assistant.
-2. Create a new project at [https://console.cloud.google.com/home/dashboard](https://console.cloud.google.com/home/dashboard), this project will be imported into Firebase later (alternatively, the project can also be created during step 4).
-3. Go to [https://console.cloud.google.com/apis/credentials/domainverification](https://console.cloud.google.com/apis/credentials/domainverification) and verify your domain via Google Webmaster Central / Search Console - [see below](#verify-your-domain).
-4. With the domain verified, go to [https://console.firebase.google.com](https://console.firebase.google.com), select import Google project and select the project you created.
-5. Then, click the cogwheel on top left and select "Project settings".
-6. Select the ['Cloud Messaging' tab](https://console.firebase.google.com/project/_/settings/cloudmessaging).
-7. Generate a new key pair under the Web configuration listing at the bottom of the page. To view the private key click the three dots to the right and 'Show private key'.
-8. Select the ['Service Accounts' tab](https://console.firebase.google.com/project/_/settings/serviceaccounts/adminsdk).
-9. Get the email address for the project under the text that says "Firebase service account" for reference. This is not what you have to insert in `vapid_email`! You'll have to insert your Google account e-mail there.
+1. Create a new project at [https://console.cloud.google.com/home/dashboard](https://console.cloud.google.com/home/dashboard), this project will be imported into Firebase later (alternatively, the project can also be created in the next step).
+2. Go to [https://console.firebase.google.com](https://console.firebase.google.com), and click the "Add project" button
+3. Choose your Google Cloud project for the name field (or create a new one). Decline analytics.
+4. Then, click the cogwheel on top left and select "Project settings".
+5. Select the "Cloud Messaging" tab.
+6. Generate a new key pair in "Web configuration" at the bottom of the page. Add the public key as `vapid_pub_key` in the config, then choose the 3 dots, and copy the private key for `vapid_prv_key` in the config.
+7. Input your Google email as `vapid_email` in the config.
 
 ### Setting up your browser
 
@@ -108,10 +106,9 @@ Assuming you have already configured the platform:
 {% my profile badge %}
 
 1. Open Home Assistant in Chrome or Firefox and load profile page by clicking the My button above or by clicking on the badge next to the Home Assistant title in the sidebar. Assuming you have met all the [requirements](#requirements) above then you should see a new slider for Push Notifications. If the slider is greyed out, ensure you are viewing Home Assistant via its external HTTPS address (and that you have configured the `notify` HTML5 integration in Home Assistant). If the slider is not visible, ensure you are not in the user configuration (Sidebar, Configuration, Users, View User).
-2. Slide it to the on position.
-3. Name the device you're using in the alert that appears.
-4. Within a few seconds you should be prompted to allow notifications from Home Assistant.
-5. Assuming you accept, that's all there is to it!
+2. Turn on the slider, and name the device you're using in the alert that appears.
+3. Within a few seconds you should be prompted to allow notifications from Home Assistant.
+4. Assuming you accept, that's all there is to it!
 
 **Note:** If you aren't prompted for a device name when enabling notifications, open the `html5_push_registrations.conf` file in your configuration directory. You will see a new entry for the browser you just added. Rename it from `unnamed device` to a name of your choice, which will make it easier to identify later. _Do not change anything else in this file!_ You need to restart Home Assistant after making any changes to the file.
 
@@ -243,7 +240,7 @@ data:
 
 You can dismiss notifications by using service html5.dismiss like so:
 
-```json
+```yaml
 target: ['my phone']
 data:
   tag: notification_tag
@@ -337,28 +334,3 @@ If you still have the problem, even with mentioned rule, try to add this code:
     proxy_set_header Authorization $http_authorization;
     proxy_pass_header Authorization;
 ```
-
-#### Verify your domain
-
-If you need to verify domain ownership with Google Webmaster Central/Search Console while configuring this component, follow these steps:
-
-##### HTML file verification (only works for `/local` URLs)
-
-1. Enter your domain and add `/local` at the end, e.g., `https://example.com:8123/local`
-2. Select HTML file verification and download the google*.html file.
-3. Create a directory named `www` in your Home Assistant configuration directory (`/config/` share from Samba add-on).
-4. Place the downloaded `google*.html` file in the `www` directory.
-5. RESTART Home Assistant. **This is important!**
-6. Verify the file can be accessed in the browser, e.g., `https://example.com:8123/local/google123456789.html` (change filename). You should see a plain text message saying "google-site-verification: ...". If you see "404: Not Found" or something else, retry the above steps.
-7. Go back to Google Webmaster Central/Search Console and proceed with the verification.
-
-##### DNS verification (only if you control your DNS record or use DuckDNS)
-
-1. Enter your domain's base URL, like `https://example.com:8123/`
-2. Select DNS verification. If you're asked to choose your DNS provider, choose "Any DNS provider" or "Other".
-3. Add the TXT record to your DNS. If you use DuckDNS, use the format:
-   ```text
-   https://www.duckdns.org/update?domains={your Duck DNS subdomain (the part before .duckdns.org)}&token={your Duck DNS token}&txt={google-site-verification record}
-   ```
-4. Wait until the changes take effect. This can be anywhere from seconds to hours, so be patient. You can use [this site to test it](https://www.digwebinterface.com/).
-5. Go back to Google Webmaster Central/Search Console and proceed with the verification.

source/_integrations/input_button.markdown

@@ -67,7 +67,7 @@ means we can use it in our automations. For example:
 ```yaml
 trigger:
   - platform: state
-    entity_id: button.my_button
+    entity_id: input_button.my_button
 action:
   - service: notify.frenck
     data:

source/_integrations/intellifire.markdown

@@ -9,6 +9,9 @@ ha_codeowners:
   - '@jeeftor'
 ha_domain: intellifire
 ha_config_flow: true
+ha_platforms:
+  - binary_sensor
+  - sensor
 ---
 
 IntelliFire Wi-Fi fireplace modules provide app-based and Alexa control to various fireplaces. The modules do expose an unencrypted HTTP endpoint on the network that provides status information. This integration will read that URL and create a set of sensors displaying the current fireplace state.
@@ -23,7 +26,7 @@ The following sensors are available as either a **Binary Sensor** when dealing w
 
 ### Binary Sensors
 
-- **Power Sensor**: Whether the fire is on.
+- **Flame Sensor**: Whether the fire is on.
 - **Pilot Light Sensor**: Whether the pilot light is turned on.
 - **Timer Sensor**: Whether the sleep timer is turned on.
 - **Thermostat Sensor**: Whether the thermostat is turned on.

source/_integrations/iqvia.markdown

@@ -10,6 +10,7 @@ ha_codeowners:
   - '@bachya'
 ha_domain: iqvia
 ha_platforms:
+  - diagnostics
   - sensor
 ---
 

source/_integrations/knx.markdown

@@ -27,6 +27,7 @@ ha_quality_scale: silver
 ha_platforms:
   - binary_sensor
   - button
+  - diagnostics
   - climate
   - cover
   - fan

source/_integrations/konnected.markdown

@@ -6,11 +6,10 @@ ha_category:
   - Binary Sensor
   - Switch
   - Sensor
-ha_iot_class: Local Polling
+ha_iot_class: Local Push
 ha_release: '0.70'
 ha_codeowners:
   - '@heythisisnate'
-  - '@kit-klein'
 ha_config_flow: true
 ha_domain: konnected
 ha_ssdp: true

source/_integrations/lametric.markdown

@@ -8,6 +8,7 @@ ha_iot_class: Cloud Push
 ha_release: 0.49
 ha_codeowners:
   - '@robbiet480'
+  - '@frenck'
 ha_domain: lametric
 ha_platforms:
   - notify

source/_integrations/launch_library.markdown

@@ -10,7 +10,9 @@ ha_codeowners:
   - '@DurgNomis-drol'
 ha_domain: launch_library
 ha_platforms:
+  - diagnostics
   - sensor
+ha_config_flow: true
 ---
 
 The `launch_library` sensor will provide you with information about the next planned space launch and SpaceX Starship event.
@@ -20,4 +22,3 @@ The `launch_library` sensor will provide you with information about the next pla
 The data this platform presents comes from [launchlibrary.net][launchlibrary].
 
 [launchlibrary]: https://launchlibrary.net/
-

source/_integrations/light.mqtt.markdown

@@ -311,7 +311,7 @@ rgb_value_template:
   required: false
   type: string
 schema:
-  description: The schema to use. Must be `default` or omitted to select the default schema".
+  description: The schema to use. Must be `default` or omitted to select the default schema.
   required: false
   type: string
   default: default
@@ -656,7 +656,7 @@ retain:
   type: boolean
   default: false
 schema:
-  description: The schema to use. Must be `json` to select the JSON schema".
+  description: The schema to use. Must be `json` to select the JSON schema.
   required: false
   type: string
   default: default
@@ -1012,7 +1012,7 @@ red_template:
   required: false
   type: string
 schema:
-  description: The schema to use. Must be `template` to select the template schema".
+  description: The schema to use. Must be `template` to select the template schema.
   required: false
   type: string
   default: default

source/_integrations/lookin.markdown

@@ -10,6 +10,7 @@ ha_release: 2021.11
 ha_iot_class: Local Push
 ha_codeowners:
   - '@ANMalko'
+  - '@bdraco'
 ha_domain: lookin
 ha_config_flow: true
 ha_platforms:

source/_integrations/luftdaten.markdown

@@ -10,8 +10,10 @@ ha_config_flow: true
 ha_quality_scale: gold
 ha_codeowners:
   - '@fabaff'
+  - '@frenck'
 ha_domain: luftdaten
 ha_platforms:
+  - diagnostics
   - sensor
 ---
 

source/_integrations/mazda.markdown

@@ -14,6 +14,7 @@ ha_codeowners:
   - '@bdr99'
 ha_domain: mazda
 ha_platforms:
+  - diagnostics
   - device_tracker
   - lock
   - sensor

source/_integrations/mobile_app.markdown

@@ -7,7 +7,7 @@ ha_release: 0.89
 ha_config_flow: true
 ha_quality_scale: internal
 ha_codeowners:
-  - '@robbiet480'
+  - '@home-assistant/core'
 ha_domain: mobile_app
 ha_iot_class: Local Push
 ha_platforms:

source/_integrations/motion_blinds.markdown

@@ -19,6 +19,7 @@ The integration allows you to control [Motion Blinds](https://motionblinds.com/)
 Additionally the following brands have been reported to also work with this integration:
 
 - [Motion Blinds](https://motionblinds.com/)
+- [Smart Blinds](https://www.smartblinds.nl/)
 - [Dooya](http://www.dooya.com/)
 - [Bloc Blinds](https://www.blocblinds.com/)
 - [Brel Home](https://www.brel-home.nl/)

source/_integrations/nam.markdown

@@ -11,6 +11,7 @@ ha_codeowners:
 ha_domain: nam
 ha_platforms:
   - button
+  - diagnostics
   - sensor
 ha_quality_scale: platinum
 ha_zeroconf: true

source/_integrations/nanoleaf.markdown

@@ -13,6 +13,7 @@ ha_release: 0.67
 ha_domain: nanoleaf
 ha_platforms:
   - button
+  - diagnostics
   - light
 ha_zeroconf: true
 ha_ssdp: true

source/_integrations/nest.markdown

@@ -19,6 +19,7 @@ ha_dhcp: true
 ha_platforms:
   - binary_sensor
   - camera
+  - diagnostics
   - climate
   - sensor
 ---

source/_integrations/netatmo.markdown

@@ -18,6 +18,7 @@ ha_domain: netatmo
 ha_homekit: true
 ha_platforms:
   - camera
+  - diagnostics
   - climate
   - light
   - sensor
@@ -105,7 +106,7 @@ It is therefore recommended to use [an individual development account](#developm
 
 </div>
 
-To be able to receive events from [Netatmo](https://www.netatmo.com/en-gb/), your Home Assistant instance needs to be accessible from the web over port `80` or `443`. To achieve this you can either use your Nabu Casa account or for example Duck DNS ([Home Assistant instructions](/addons/duckdns/)). You also need to have the external URL configured in the Home Assistant [configuration](/docs/configuration/basic).
+To be able to receive events from [Netatmo](https://www.netatmo.com/en-gb/), your Home Assistant instance needs to be accessible from the web over port `443`. To achieve this you can either use your Nabu Casa account or for example Duck DNS ([Home Assistant instructions](/addons/duckdns/)). You also need to have the external URL configured in the Home Assistant [configuration](/docs/configuration/basic).
 
 Events coming in from Netatmo will be available as an event in Home Assistant and are fired as `netatmo_event`, along with their data. You can use these events to trigger automations.
 
@@ -213,6 +214,12 @@ to declare a new application in the [Netatmo Developer Page](https://dev.netatmo
 
 Sign in using your username and password from your regular Netatmo account.
 
+<div class='note warning'>
+ 
+In your Netatmo Application configuration, do not enter a 'redirect URI' or a 'webhook URI'.  The 'webhook URI' is automatically registered by this integration based on the external URL configured in the Home Assistant [configuration](/docs/configuration/basic).
+  
+</div>
+
 Next, add the following lines to your `configuration.yaml`:
 
 ```yaml
@@ -242,6 +249,10 @@ After completing the configuration flow, the Netatmo integration will be availab
 
 ## Troubleshooting
 
+### Receiving events
+
+To confirm your Home Assistant instance is receiving events via webhooks, you can listen to `netatmo_event` in {% my developer_events title="Developer Tools -> Events" %}.
+
 ### Light
 
 If the lights show as unavailable the issue usually is that webhook is banned by Netatmo. To solve that [unregister](#un-register-webhooks) the webhook, go to the [Netatmo Developer Page](https://dev.netatmo.com/) to unban your webhook and then [register](#un-register-webhooks) the webhook.

source/_integrations/nina.markdown

@@ -18,3 +18,13 @@ The [NINA](https://www.bbk.bund.de/DE/Warnung-Vorsorge/Warn-App-NINA/warn-app-ni
 For each county/city it creates warning slots that change to Unsafe when warnings are present. The text of the warning and the metadata are stored in the attributes of the slots.
 
 {% include integrations/config_flow.md %}
+
+### Attributes
+
+| Attribute    | Description                            |
+| ------------ | -------------------------------------- |
+| `Headline` | *(str)* Official headline of the warning. |
+| `ID` | *(str)* Individual ID for each warning. |
+| `Sent` | *(time)* Transmission time and date (UTC) of the issued warning. |
+| `Start` | *(time)* Starting time and date (UTC) of the issued warning. Can be empty. |
+| `Expires` | *(time)* Expiration time and date (UTC) of the issued warning. Can be empty. |

source/_integrations/nmap_tracker.markdown

@@ -9,8 +9,6 @@ ha_domain: nmap_tracker
 ha_platforms:
   - device_tracker
 ha_config_flow: true
-ha_codeowners:
-  - '@bdraco'
 ---
 
 As an alternative to the router-based device tracking, it is possible to directly scan the network for devices by using Nmap. The IP addresses to scan can be specified in any format that Nmap understands, including the network-prefix notation (`192.168.1.1/24`) and the range notation (`192.168.1.1-255`).

source/_integrations/notion.markdown

@@ -13,6 +13,7 @@ ha_codeowners:
 ha_domain: notion
 ha_platforms:
   - binary_sensor
+  - diagnostics
   - sensor
 ---
 

source/_integrations/onewire.markdown

@@ -12,6 +12,7 @@ ha_codeowners:
 ha_domain: onewire
 ha_platforms:
   - binary_sensor
+  - diagnostics
   - sensor
   - switch
 ---

source/_integrations/onvif.markdown

@@ -12,6 +12,7 @@ ha_config_flow: true
 ha_platforms:
   - binary_sensor
   - camera
+  - button
   - sensor
 ---
 

source/_integrations/open_meteo.markdown

@@ -10,6 +10,7 @@ ha_codeowners:
   - '@frenck'
 ha_domain: open_meteo
 ha_platforms:
+  - diagnostics
   - weather
 ---
 

source/_integrations/openuv.markdown

@@ -13,6 +13,7 @@ ha_codeowners:
 ha_domain: openuv
 ha_platforms:
   - binary_sensor
+  - diagnostics
   - sensor
 ---
 

source/_integrations/overkiz.markdown

@@ -18,23 +18,24 @@ ha_release: 2022.2
 ha_config_flow: true
 ha_iot_class: Cloud Polling
 ha_codeowners:
-  - '@tetienne'
   - '@imicknl'
   - '@vlebourl'
+  - '@tetienne'
 ha_domain: overkiz
 ha_dhcp: true
 ha_zeroconf: true
 ha_platforms:
   - binary_sensor
   - button
+  - diagnostics
   - cover
   - light
   - lock
   - number
   - scene
-  - select
   - sensor
   - siren
+  - select
   - switch
 ---
 

source/_integrations/p1_monitor.markdown

@@ -10,6 +10,7 @@ ha_codeowners:
   - '@klaasnicolaas'
 ha_domain: p1_monitor
 ha_platforms:
+  - diagnostics
   - sensor
 ha_quality_scale: platinum
 ---

source/_integrations/philips_js.markdown

@@ -15,6 +15,7 @@ ha_platforms:
   - light
   - media_player
   - remote
+  - switch
 ---
 
 The `philips_js` platform allows you to control Philips TVs which expose the [jointSPACE](http://jointspace.sourceforge.net/) JSON-API.

source/_integrations/picnic.markdown

@@ -25,10 +25,10 @@ This integration provides the following sensors. Some sensors are disabled by de
 | ------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------- |
 | Cart items count               | The amount of different products currently in the cart.                                                                                             |
 | Cart total price               | The total price for products currently in the cart.                                                                                                 |
-| Selected slot start            | Start of the selected delivery slot, `unavailable` if none is selected.                                                                             |
-| Selected slot end              | End of the selected delivery slot, `unavailable` if none is selected.                                                                               |
-| Selected slot max order time   | Maximum time it's still possible to place an order for the selected delivery slot, `unavailable` if none is selected.                               |
-| Selected slot min order value  | The minimum order value needed to be able to place an order for the selected delivery window slot, `unavailable` if none is selected.               |
+| Selected slot start            | Start of the selected delivery slot, `unknown` if none is selected.                                                                             |
+| Selected slot end              | End of the selected delivery slot, `unknown` if none is selected.                                                                               |
+| Selected slot max order time   | Maximum time it's still possible to place an order for the selected delivery slot, `unknown` if none is selected.                               |
+| Selected slot min order value  | The minimum order value needed to be able to place an order for the selected delivery window slot, `unknown` if none is selected.               |
 | Last order slot start          | Start of the last placed order's delivery slot                                                                                                      |
 | Last order slot end            | End of the last placed order's delivery slot                                                                                                        |
 | Last order status              | Status of the last order, either `CURRENT`, `CANCELLED` or `COMPLETED`. Will only transition to `COMPLETED` after the invoice email has been sent.  |
@@ -38,4 +38,4 @@ This integration provides the following sensors. Some sensors are disabled by de
 | Next delivery ETA start        | Start of the ETA window of the next delivery, will get more precise if the driver is underway. |
 | Next delivery ETA end          | End of the ETA window of the next delivery. |
 | Next delivery slot start       | Start of the next delivery's delivery slot. |
-| Next delivery slot end         | End of the next delivery's delivery slot. |
+| Next delivery slot end         | End of the next delivery's delivery slot. |

source/_integrations/proxmoxve.markdown

@@ -6,7 +6,6 @@ ha_category:
 ha_release: 0.103
 ha_iot_class: Local Polling
 ha_codeowners:
-  - '@k4ds3'
   - '@jhollowe'
   - '@Corbeno'
 ha_domain: proxmoxve

source/_integrations/pvoutput.markdown

@@ -11,7 +11,9 @@ ha_codeowners:
 ha_config_flow: true
 ha_domain: pvoutput
 ha_platforms:
+  - diagnostics
   - sensor
+ha_quality_scale: platinum
 ---
 
 The PVOutput integration consumes information from [PVOutput](https://pvoutput.org/) which was uploaded by your solar photovoltaic (PV) system.

source/_integrations/qnap.markdown

@@ -5,8 +5,6 @@ ha_category:
   - System Monitor
 ha_release: 0.38
 ha_iot_class: Local Polling
-ha_codeowners:
-  - '@colinodell'
 ha_domain: qnap
 ha_platforms:
   - sensor

source/_integrations/rainforest_eagle.markdown

@@ -11,6 +11,7 @@ ha_codeowners:
   - '@jcalbert'
 ha_domain: rainforest_eagle
 ha_platforms:
+  - diagnostics
   - sensor
 ha_config_flow: true
 ha_dhcp: true

source/_integrations/rainmachine.markdown

@@ -14,6 +14,7 @@ ha_codeowners:
 ha_domain: rainmachine
 ha_platforms:
   - binary_sensor
+  - diagnostics
   - sensor
   - switch
 ha_zeroconf: true

source/_integrations/rdw.markdown

@@ -14,6 +14,7 @@ ha_codeowners:
 ha_domain: rdw
 ha_platforms:
   - binary_sensor
+  - diagnostics
   - sensor
 ---
 

source/_integrations/recollect_waste.markdown

@@ -10,6 +10,7 @@ ha_codeowners:
   - '@bachya'
 ha_config_flow: true
 ha_platforms:
+  - diagnostics
   - sensor
 ---
 

source/_integrations/renault.markdown

@@ -16,6 +16,7 @@ ha_domain: renault
 ha_platforms:
   - binary_sensor
   - button
+  - diagnostics
   - device_tracker
   - sensor
   - select

source/_integrations/repetier.markdown

@@ -8,6 +8,7 @@ ha_release: 0.94
 ha_iot_class: Local Polling
 ha_codeowners:
   - '@MTrab'
+  - '@ShadowBr0ther'
 ha_domain: repetier
 ha_platforms:
   - sensor