Merge branch 'current' into next

2025-07-18 23:06:58 +00:00 · 2023-12-07 11:16:27 +01:00 · 2023-12-07 11:16:27 +01:00 · ded85ace2a
commit ded85ace2a
parent d5377b2ea1 ce17711b61
113 changed files with 2697 additions and 262 deletions
--- a/34
+++ b/34
@ -84,7 +84,7 @@ source/_integrations/bge.markdown @tronikos
 source/_integrations/binary_sensor.markdown @home-assistant/core
 source/_integrations/bizkaibus.markdown @UgaitzEtxebarria
 source/_integrations/blebox.markdown @bbx-a @riokuu
-source/_integrations/blink.markdown @fronzbot
+source/_integrations/blink.markdown @fronzbot @mkmer
 source/_integrations/bliss_automation.markdown @starkillerOG
 source/_integrations/bloc_blinds.markdown @starkillerOG
 source/_integrations/bluemaestro.markdown @bdraco
@ -155,6 +155,7 @@ source/_integrations/deluge.markdown @tkdrob
 source/_integrations/demo.markdown @home-assistant/core
 source/_integrations/denonavr.markdown @ol-iver @starkillerOG
 source/_integrations/derivative.markdown @afaucogney
+source/_integrations/devialet.markdown @fwestenberg
 source/_integrations/device_automation.markdown @home-assistant/core
 source/_integrations/device_tracker.markdown @home-assistant/core
 source/_integrations/devolo_home_control.markdown @2Fake @Shutgun
@ -183,9 +184,9 @@ source/_integrations/dwd_weather_warnings.markdown @runningman84 @stephan192 @an
 source/_integrations/dynalite.markdown @ziv1234
 source/_integrations/eastron.markdown @DCSBL
 source/_integrations/easyenergy.markdown @klaasnicolaas
-source/_integrations/ecobee.markdown @marthoc @marcolivierarsenault
+source/_integrations/ecobee.markdown @marcolivierarsenault
 source/_integrations/ecoforest.markdown @pjanuario
-source/_integrations/econet.markdown @vangorra @w1ll1am23
+source/_integrations/econet.markdown @w1ll1am23
 source/_integrations/ecovacs.markdown @OverloadUT @mib1185
 source/_integrations/ecowitt.markdown @pvizeli
 source/_integrations/efergy.markdown @tkdrob
@ -207,14 +208,12 @@ source/_integrations/energyzero.markdown @klaasnicolaas
 source/_integrations/enigma2.markdown @fbradyirl
 source/_integrations/enmax.markdown @tronikos
 source/_integrations/enocean.markdown @bdurrer
-source/_integrations/enphase_envoy.markdown @bdraco @cgarwood @dgomes @joostlek
+source/_integrations/enphase_envoy.markdown @bdraco @cgarwood @dgomes @joostlek @catsmanac
 source/_integrations/entur_public_transport.markdown @hfurubotten
 source/_integrations/environment_canada.markdown @gwww @michaeldavie
-source/_integrations/envisalink.markdown @ufodone
 source/_integrations/ephember.markdown @ttroy50
 source/_integrations/epson.markdown @pszafer
 source/_integrations/epsonworkforce.markdown @ThaStealth
-source/_integrations/eq3btsmart.markdown @rytilahti
 source/_integrations/escea.markdown @lazdavila
 source/_integrations/esera_onewire.markdown @garbled1 @epenet
 source/_integrations/esphome.markdown @OttoWinter @jesserockz @kbx81 @bdraco
@ -226,7 +225,7 @@ source/_integrations/evohome.markdown @zxdavb
 source/_integrations/ezviz.markdown @RenierM26 @baqs
 source/_integrations/faa_delays.markdown @ntilley905
 source/_integrations/fan.markdown @home-assistant/core
-source/_integrations/fastdotcom.markdown @rohankapoorcom
+source/_integrations/fastdotcom.markdown @rohankapoorcom @erwindouna
 source/_integrations/fibaro.markdown @rappenze
 source/_integrations/file.markdown @fabaff
 source/_integrations/file_upload.markdown @home-assistant/core
@ -290,7 +289,6 @@ source/_integrations/gpsd.markdown @fabaff
 source/_integrations/gree.markdown @cmroche
 source/_integrations/greeneye_monitor.markdown @jkeljo
 source/_integrations/group.markdown @home-assistant/core
-source/_integrations/growatt_server.markdown @muppet3000
 source/_integrations/guardian.markdown @bachya
 source/_integrations/habitica.markdown @ASMfreaK @leikoilja
 source/_integrations/hardware.markdown @home-assistant/core
@ -387,6 +385,7 @@ source/_integrations/kitchen_sink.markdown @home-assistant/core
 source/_integrations/kmtronic.markdown @dgomes
 source/_integrations/knx.markdown @Julius2342 @farmio @marvin-w
 source/_integrations/kodi.markdown @OnFreund
+source/_integrations/komfovent.markdown @ProstoSanja
 source/_integrations/konnected.markdown @heythisisnate
 source/_integrations/kostal_plenticore.markdown @stegm
 source/_integrations/kraken.markdown @eifinger
@ -407,6 +406,7 @@ source/_integrations/lg_netcast.markdown @Drafteed
 source/_integrations/lidarr.markdown @tkdrob
 source/_integrations/life360.markdown @pnbruckner
 source/_integrations/light.markdown @home-assistant/core
+source/_integrations/linear_garage_door.markdown @IceBotYT
 source/_integrations/linux_battery.markdown @fabaff
 source/_integrations/litejet.markdown @joncar
 source/_integrations/litterrobot.markdown @natekspencer @tkdrob
@ -471,7 +471,7 @@ source/_integrations/msteams.markdown @peroyvind
 source/_integrations/mullvad.markdown @meichthys
 source/_integrations/mutesync.markdown @currentoor
 source/_integrations/my.markdown @home-assistant/core
-source/_integrations/mypermobil @IsakNyberg
+source/_integrations/mypermobil.markdown @IsakNyberg
 source/_integrations/mysensors.markdown @MartinHjelmare @functionpointer
 source/_integrations/mystrom.markdown @fabaff
 source/_integrations/nam.markdown @bieniu
@ -538,6 +538,7 @@ source/_integrations/oralb.markdown @bdraco @Lash-L
 source/_integrations/oru.markdown @bvlaicu
 source/_integrations/oru_opower.markdown @tronikos
 source/_integrations/otbr.markdown @home-assistant/core
+source/_integrations/ourgroceries.markdown @OnFreund
 source/_integrations/overkiz.markdown @imicknl @vlebourl @tetienne @nyroDev
 source/_integrations/ovo_energy.markdown @timmo001
 source/_integrations/p1_monitor.markdown @klaasnicolaas
@ -569,6 +570,7 @@ source/_integrations/profiler.markdown @bdraco
 source/_integrations/progettihwsw.markdown @ardaseremet
 source/_integrations/prometheus.markdown @knyar
 source/_integrations/prosegur.markdown @dgomes
+source/_integrations/proximity.markdown @mib1185
 source/_integrations/proxmoxve.markdown @jhollowe @Corbeno
 source/_integrations/prusalink.markdown @balloob
 source/_integrations/ps4.markdown @ktnrg45
@ -610,12 +612,13 @@ source/_integrations/renault.markdown @epenet
 source/_integrations/renson.markdown @jimmyd-be
 source/_integrations/reolink.markdown @starkillerOG
 source/_integrations/repairs.markdown @home-assistant/core
-source/_integrations/repetier.markdown @MTrab @ShadowBr0ther
+source/_integrations/repetier.markdown @ShadowBr0ther
 source/_integrations/rexel.markdown @imicknl @vlebourl @tetienne @nyroDev
 source/_integrations/rflink.markdown @javicalle
 source/_integrations/rfxtrx.markdown @danielhiversen @elupus @RobBie1221
 source/_integrations/rhasspy.markdown @balloob @synesthesiam
 source/_integrations/ridwell.markdown @bachya
+source/_integrations/ring.markdown @sdb9696
 source/_integrations/risco.markdown @OnFreund
 source/_integrations/rituals_perfume_genie.markdown @milanmeu @frenck
 source/_integrations/rmvtransport.markdown @cgtobi
@ -716,7 +719,7 @@ source/_integrations/stiebel_eltron.markdown @fucm
 source/_integrations/stookalert.markdown @fwestenberg @frenck
 source/_integrations/stookwijzer.markdown @fwestenberg
 source/_integrations/stream.markdown @hunterjm @uvjustin @allenporter
-source/_integrations/stt.markdown @home-assistant/core @pvizeli
+source/_integrations/stt.markdown @home-assistant/core
 source/_integrations/subaru.markdown @G-Two
 source/_integrations/suez_water.markdown @ooii
 source/_integrations/sun.markdown @Swamp-Ig
@ -766,7 +769,7 @@ source/_integrations/todoist.markdown @boralyl
 source/_integrations/tolo.markdown @MatthiasLohr
 source/_integrations/tomorrowio.markdown @raman325 @lymanepp
 source/_integrations/totalconnect.markdown @austinmroczek
-source/_integrations/tplink.markdown @rytilahti @thegardenmonkey
+source/_integrations/tplink.markdown @rytilahti @thegardenmonkey @bdraco
 source/_integrations/tplink_omada.markdown @MarkGodwin
 source/_integrations/traccar.markdown @ludeeus
 source/_integrations/tractive.markdown @Danielhiversen @zhulik @bieniu
@ -776,7 +779,7 @@ source/_integrations/trafikverket_train.markdown @gjohansson-ST
 source/_integrations/trafikverket_weatherstation.markdown @gjohansson-ST
 source/_integrations/transmission.markdown @engrbm87 @JPHutchins
 source/_integrations/trend.markdown @jpbede
-source/_integrations/tts.markdown @home-assistant/core @pvizeli
+source/_integrations/tts.markdown @home-assistant/core
 source/_integrations/tuya.markdown @Tuya @zlinoliver @frenck
 source/_integrations/twentemilieu.markdown @frenck
 source/_integrations/twinkly.markdown @dr1rrb @Robbie1221 @Olen
@ -797,16 +800,17 @@ 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/v2c.markdown @dgomes
 source/_integrations/vacuum.markdown @home-assistant/core
 source/_integrations/vallox.markdown @andre-richter @slovdahl @viiru-
 source/_integrations/velbus.markdown @Cereal2nd @brefra
 source/_integrations/velux.markdown @Julius2342
 source/_integrations/venstar.markdown @garbled1 @jhollowe
-source/_integrations/verisure.markdown @frenck
 source/_integrations/vermont_castings.markdown @jeeftor
 source/_integrations/versasense.markdown @imstevenxyz
 source/_integrations/version.markdown @ludeeus
 source/_integrations/vesync.markdown @markperdue @webdjoe @thegardenmonkey
+source/_integrations/vicare.markdown @CFenner
 source/_integrations/vilfo.markdown @ManneW
 source/_integrations/vivotek.markdown @HarlemSquirrel
 source/_integrations/vizio.markdown @raman325
@ -869,7 +873,7 @@ source/_integrations/zengge.markdown @emontnemery
 source/_integrations/zeroconf.markdown @bdraco
 source/_integrations/zerproc.markdown @emlove
 source/_integrations/zeversolar.markdown @kvanzuijlen
-source/_integrations/zha.markdown @dmulcahey @adminiuga @puddly
+source/_integrations/zha.markdown @dmulcahey @adminiuga @puddly @TheJulianJES
 source/_integrations/zodiac.markdown @JulienTant
 source/_integrations/zone.markdown @home-assistant/core
 source/_integrations/zoneminder.markdown @rohankapoorcom
--- a/_config.yml
+++ b/_config.yml
@ -109,9 +109,9 @@ social:

 # Home Assistant release details
 current_major_version: 2023
-current_minor_version: 11
-current_patch_version: 3
-date_released: 2023-11-22
+current_minor_version: 12
+current_patch_version: 0
+date_released: 2023-12-06

 # Either # or the anchor link to latest release notes in the blog post.
 # Must be prefixed with a # and have double quotes around it.
--- a/source/_data/glossary.yml
+++ b/source/_data/glossary.yml
@ -126,6 +126,8 @@
  excerpt: >
    Each integration in Home Assistant has a unique identifier: The domain.
    It is often shown as the first part (before the dot) of entity IDs.
+  aliases:
+    - domains
 - term: Entity
  definition: |-
    An entity represents a sensor, actor, or function in Home Assistant. Entities are used to monitor physical properties or to control other entities. An entity is usually part of a device or a service. Entities have states.
@ -159,6 +161,8 @@
  definition: >-
    Groups are a way to organize your entities into a single unit.
  link: /integrations/group/
+  aliases:
+    - groups
 - term: HASS
  definition: >-
    HASS or [hass](/docs/tools/hass/) is often used as an abbreviation for
@ -255,10 +259,14 @@
  definition: >-
    You can use notifications to send messages, pictures, and more, to devices.
  link: /integrations/#notifications
- term: Packages
+  aliases:
+    - notifications
+- term: Package
  definition: >
    Packages allow you to bundle different component configurations together.
  link: /docs/configuration/packages/
+  aliases:
+    - packages
 - term: Platform
  definition: >-
    Platforms are building blocks provided by some integrations to be used by
@ -270,6 +278,8 @@
    Platforms are building blocks provided by some integrations to be used by
    other integrations.
  link: /docs/configuration/platform_options/
+  aliases:
+    - platforms
 - term: Reload
  definition: >-
    Applies the changes made to the Home Assistant configuration files. Changes
@ -306,7 +316,7 @@
  link: /integrations/sensor/
  aliases:
    - sensors
- term: Selectors
+- term: Selector
  definition: >-
    Selectors are components for the user interface. Some selectors can,
    for example, show a toggle button to turn something on or off, while another
@ -316,6 +326,8 @@
    Selectors are components for the user interface. Like toggle, dropdown,
    and more.
  link: /docs/blueprint/selectors/
+  aliases:
+    - selectors
 - term: Service
  definition: |-
    The term service has 2 meanings in Home Assistant:
--- a/source/_docs/configuration/templating.markdown
+++ b/source/_docs/configuration/templating.markdown
@ -115,7 +115,7 @@ Not supported in [limited templates](#limited-templates).
 - `states.sensor.temperature` returns the state object for `sensor.temperature` (avoid when possible, see note below).
 - `states` can also be used as a function, `states(entity_id, rounded=False, with_unit=False)`, which returns the state string (not the state object) of the given entity, `unknown` if it doesn't exist, and `unavailable` if the object exists but is not available.
  - The optional arguments `rounded` and `with_unit` control the formatting of sensor state strings, please see the [examples](#formatting-sensor-states) below.
- `states.sensor.temperature.state_with_unit` formats the state string in the same was is if calling `states('sensor.temperature', rounded=True, with_unit=True)`.
+- `states.sensor.temperature.state_with_unit` formats the state string in the same way as if calling `states('sensor.temperature', rounded=True, with_unit=True)`.
 - `is_state` compares an entity's state with a specified state or list of states and returns `True` or `False`. `is_state('device_tracker.paulus', 'home')` will test if the given entity is the specified state. `is_state('device_tracker.paulus', ['home', 'work'])` will test if the given entity is any of the states in the list.
 - `state_attr('device_tracker.paulus', 'battery')` will return the value of the attribute or None if it doesn't exist.
 - `is_state_attr('device_tracker.paulus', 'battery', 40)` will test if the given entity attribute is the specified state (in this case, a numeric value). Note that the attribute can be `None` and you want to check if it is `None`, you need to use `state_attr('sensor.my_sensor', 'attr') is none` or `state_attr('sensor.my_sensor', 'attr') == None` (note the difference in the capitalization of none in both versions).
--- a/source/_docs/energy/battery.markdown
+++ b/source/_docs/energy/battery.markdown
@ -17,12 +17,4 @@ Some battery vendors have an API to integrate the data into your Home Assistant

 ### Using a CT clamp sensor

-CT clamp sensors measure your energy usage by looking at the current passing through an electrical wire. This makes it possible to calculate the energy usage. In Home Assistant we have support for off-the-shelf CT clamp sensors and you can build your own.
-
-The off-the-shelf solution that we advise is the [Shelly EM](https://www.shelly.com/en/products/shop/shelly-em-120a/shelly-em-50a?tracking=A7FsiPIfUWsFpnfKHa8SRyUYLXjr2hPq). The device has a local API, updates are pushed to Home Assistant and it has a high quality [integration](/integrations/shelly/).
-
-You can build your own using ESPHome's [CT Clamp Current sensor](https://esphome.io/components/sensor/ct_clamp.html) or energy meter sensors like the [ATM90E32](https://esphome.io/components/sensor/atm90e32.html). For the DIY route, check out [this video by digiblur](https://www.youtube.com/watch?v=n2XZzciz0s4) to get started.
-
-_Attention! Installing CT clamp sensor devices requires opening your electrical cabinet. This work should be done by someone familiar with electrical wiring. Your qualified installer will know how to do this._
-
-_Disclaimer: Some links on this page are affiliate links._
+{% include energy/ct_clamp.md %}
--- a/source/_docs/energy/electricity-grid.markdown
+++ b/source/_docs/energy/electricity-grid.markdown
@ -63,13 +63,7 @@ In countries like Germany, SML (Smart Message Language) is used typically. ESPHo

 ### Using a CT clamp sensor

-CT clamp sensors measure your energy usage by looking at the current passing through an electrical wire. This makes it possible to calculate the energy usage. In Home Assistant we have support for off-the-shelf CT clamp sensors and you can build your own.
-
-The off-the-shelf solution that we advise is the [Shelly EM](https://www.shelly.com/en/products/shop/shelly-em-120a/shelly-em-50a?tracking=A7FsiPIfUWsFpnfKHa8SRyUYLXjr2hPq). The device has a local API, updates are pushed to Home Assistant and it has a high quality [integration](/integrations/shelly/).
-
-You can build your own using ESPHome's [CT Clamp Current sensor](https://esphome.io/components/sensor/ct_clamp.html) or energy meter sensors like the [ATM90E32](https://esphome.io/components/sensor/atm90e32.html) or [PZEM-004T V3](https://esphome.io/components/sensor/pzemac.html). For the DIY route, check out [this video by digiblur](https://www.youtube.com/watch?v=n2XZzciz0s4) to get started.
-
-_Attention! Installing CT clamp sensor devices requires opening your electrical cabinet. This work should be done by someone familiar with electrical wiring. Your qualified installer will know how to do this._
+{% include energy/ct_clamp.md %}

 ### Data provided by your energy provider

--- a/source/_docs/energy/solar-panels.markdown
+++ b/source/_docs/energy/solar-panels.markdown
@ -15,15 +15,7 @@ Home Assistant will need to know the amount of energy that is being produced. Th

 ### Using a CT clamp sensor

-CT clamp sensors measure the instantaneous current passing through an electrical wire. To translate this into electrical power (W) you also need a voltage measurement, because Power = Current x Voltage.
-
-In Home Assistant we have support for off-the-shelf CT clamp sensors and you can build your own with ESPHome's [CT Clamp Current sensor](https://esphome.io/components/sensor/ct_clamp.html).
-
-The off-the-shelf solution that we advise is the [Shelly EM](https://www.shelly.com/en/products/shop/shelly-em-120a/shelly-em-50a?tracking=A7FsiPIfUWsFpnfKHa8SRyUYLXjr2hPq). The device has a local API, updates are pushed to Home Assistant and it has a high quality [integration](/integrations/shelly/).
-
-_Attention! Installing CT clamp sensor devices requires opening your electrical cabinet. This work should be done by someone familiar with electrical wiring. Your qualified installer will know how to do this._
-
-_Disclaimer: Some links on this page are affiliate links._
+{% include energy/ct_clamp.md %}

 ### Connecting to your inverter

--- a/source/_docs/z-wave/controllers.markdown
+++ b/source/_docs/z-wave/controllers.markdown
@ -45,6 +45,7 @@ Users should upgrade the firmware on all 700 series controllers to version 7.17.
  - Z-Wave.Me RaZberry 7 (ZME_RAZBERRY7, 700 series)
  - Z-Wave.Me RaZberry 7 Pro (ZMEERAZBERRY7_PRO or ZMEURAZBERRY7_PRO, 700 series)
  - Z-Wave.Me Razberry 2 (500 series)
+  - Z-Wave.Me Razberry 1 (300 series)

 If you are just starting out, we recommend that you purchase a 700 series controller or a Raspberry Pi module. The 700 series controllers are the more recent version (when compared to the 500 series). The 700 series controllers support SmartStart, which allows you to add a device by scanning a QR code.

--- a/source/_includes/energy/ct_clamp.md
+++ b/source/_includes/energy/ct_clamp.md
@ -0,0 +1,8 @@
+Current transformer (CT) clamp sensors measure your energy usage by looking at the current passing through an electrical wire. This makes it possible to calculate the energy usage. In Home Assistant we have support for off-the-shelf CT clamp sensors or you can build your own.
+
+- The off-the-shelf solution that we advise is the [Shelly EM](https://www.shelly.com/en/products/shop/shelly-em-120a/shelly-em-50a?tracking=A7FsiPIfUWsFpnfKHa8SRyUYLXjr2hPq). The device has a local API, updates are pushed to Home Assistant and it has a high quality [integration](/integrations/shelly/).
+- You can build your own using ESPHome's [CT Clamp Current sensor](https://esphome.io/components/sensor/ct_clamp.html) or energy meter sensors like the [ATM90E32](https://esphome.io/components/sensor/atm90e32.html). For the DIY route, check out [this video by digiblur](https://www.youtube.com/watch?v=n2XZzciz0s4) to get started.
+
+_Attention! Installing CT clamp sensor devices requires opening your electrical cabinet. This work should be done by someone familiar with electrical wiring and may require a licensed professional in some regions. Your qualified installer will know how to do this._
+
+_Disclaimer: Some links in this section are affiliate links._
--- a/source/_includes/installation/operating_system.md
+++ b/source/_includes/installation/operating_system.md
@ -6,7 +6,7 @@

 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 == 'ODROID' %}
+{% if page.installation_type == 'odroid' %}

 ## Suggested hardware

@ -161,7 +161,7 @@ Use this method only if Method 1 does not work for you.
   - This means you will lose all the data as well as the previously installed operating system.
   - Back up your data before continuing with the next step.
 2. Attach the Home Assistant boot medium ({{site.installation.types[page.installation_type].installation_media}}) to your computer.
-    {% if page.installation_type == 'ODROID' %}
+    {% if page.installation_type == 'odroid' %}
      If you are using ODROID M1, note that booting from NVMe is not supported. If you want to boot from eMMC, [update the firmware](https://github.com/home-assistant/operating-system/blob/dev/Documentation/boards/hardkernel/odroid-m1.md) before installing the image.

      If you are using a [Home Assistant Blue](/blue) or ODROID N2+, you can [attach your device directly](/common-tasks/os/#flashing-an-odroid-n2).
@ -265,14 +265,14 @@ If you are running an older Windows version or have a stricter network configura
 ### Download the appropriate image

 - [VirtualBox][vdi] (.vdi)
-{% if page.installation_type == 'windows' or page.installation_type == 'Linux' %}
+{% if page.installation_type == 'linux' %}
 - [KVM][qcow2] (.qcow2)
- [Vmware Workstation][vmdk] (.vmdk)
 {% elsif page.installation_type == 'alternative' %}
 - [KVM/Proxmox][qcow2] (.qcow2)
 - [VMware ESXi/vSphere][Virtual Appliance] (.ova)
 {% endif %}
 {% if page.installation_type == 'windows' %}
+- [VMware Workstation][vmdk] (.vmdk)
 - [Hyper-V][vhdx] (.vhdx)
 {% endif %}

@ -280,7 +280,7 @@ After downloading, decompress the image. If the image comes in a ZIP file, for e

 Follow this guide if you already are running a supported virtual machine hypervisor. If you are not familiar with virtual machines, install Home Assistant OS directly on a [Home Assistant Yellow](/installation/yellow), a [Raspberry Pi](/installation/raspberrypi), or an [ODROID](/installation/odroid).

-{% if page.installation_type == 'macOS' %}
+{% if page.installation_type == 'macos' %}

 - If VirtualBox is not supported on your Mac, and you have experience using virtual machines, you can try running the Home Assistant Operating System on [UTM](https://mac.getutm.app/).
 {% endif %}
@ -305,14 +305,15 @@ Minimum recommended assignments:
  content: |
    1. Create a new virtual machine.
    2. Select type **Linux** and version **Linux 2.6 / 3.x / 4.x (64-bit)**.
-    3. Select **Use an existing virtual hard disk file**, select the unzipped VDI file from above.
-    4. Edit the **Settings** of the VM and go to **System** > **Motherboard**. Select **Enable EFI**.
+    3. Under **Hardware**, select the amount of memory and number of CPUs. Then, select **Enable EFI**.
+       - Make sure **EFI** is enabled. If EFI is not enabled, HAOS won't boot.
+    4. Under **Hard Disk**, select **Use an existing virtual hard disk file**, select the unzipped VDI file from above.
    5. Then go to **Network** > **Adapter 1**. Choose **Bridged Adapter** and choose your network adapter.
    <div class="note warning">
    Please keep in mind that the bridged adapter only functions over a hardwired Ethernet connection.
    Using Wi-Fi on your VirtualBox host is unsupported.
    </div>
-    6. Then go to **Audio** and choose **Intel HD Audio** as audio controller.
+    6. Then go to <b>Audio</b> and choose <b>Intel HD Audio</b> as audio controller.
    <div class="note info">

    By default, VirtualBox does not free up unused disk space. To automatically shrink the vdi disk image
@ -326,6 +327,8 @@ Minimum recommended assignments:

    </div>

+{% unless page.installation_type == 'macos' %}
+
 - title: Unraid
  content: |
    1. Download the **.qcow2** image above and decompress it. (**Extract all** in Windows)
@ -344,8 +347,6 @@ Minimum recommended assignments:
    14. Select the name of your new VM and select the capacity number for your disk. Here, you can expand the disk to whatever your needs are. The default is 32&nbsp;GB.
    15. Select the icon of your new VM and select **start with console (VNC)**.

-{% unless page.installation_type == 'macOS' %}
-
 - title: KVM (virt-manager)
  content: |
    1. Create a new virtual machine in `virt-manager`.
@ -393,17 +394,42 @@ Minimum recommended assignments:

 {% endunless %}

-{% if page.installation_type == 'windows' or page.installation_type == 'Linux' %}
+{% if page.installation_type == 'windows' %}

- title: Vmware Workstation
+- title: VMware Workstation
  content: |
-    1. Create a new virtual machine.
-    2. Select **Custom**, make it compatible with the default of Workstation and ESX.
-    3. Choose **I will install the operating system later**, select **Linux** > **Other Linux 5.x or later kernel 64-bit**.
-    4. Select **Use Bridged Networking**.
-    5. Select **Use an existing virtual disk** and select the VMDK file above.
+    1. Start VMware Workstation and select **Create a New Virtual Machine**.
+       - Note: the exact name and location of the settings below depend on the VMware version. This procedure is based on version 17.
+    2. Select **I will install the operating system later**, then select **Linux** > **Other Linux 5.x kernel 64-bit**.
+    3. Give the VM a name, `home-assistant`, and define an easy to reach storage location, such as `C:\home-assistant`.
+    4. Specify the disk size and select **Store virtual disk as a single file**.
+    5. Select **Customize Hardware**.
+    6. Define the amount of memory and the number of cores the VM is allowed to use.
+    7. Remove the **New CD/DVD** entry. It will not be used.
+    8. Connect an Ethernet cable and make sure it is connected to your network.
+    9. Under **Network adapter**, select **Bridged: Connected directly to the physical network**.
+       - Make sure **Replicate physical network connection state** is not selected.
+       - Select **Configure Adapters**.
+       - Make sure all virtual adapters and Bluetooth devices are deselected.
+       - Select your host network adapter. Most likely, this is one of the first 2 checkboxes in the list:
+         - Select the one for Ethernet.
+         - The exact names of these adapters depend on your hardware.
+    10. At the end of the wizard, select **Finish**.
+
+      ## Edit the VM settings
+
+      11. In Windows Explorer, navigate to the storage location of your newly created VM, for example under `C:\home-assistant`.
+      12. Delete the `home-assistant.vmdk` file.
+      3. In the `Downloads` folder, find the `haos_ova_xx.x.vmdk` file. 
+         - If you haven't unzipped the archive, unzip it.
+         - Within the folder, find the `.vmdk` file and rename it to `home-assistant.vmdk`.
+         - Paste the file (not the unzipped folder) into the `C:\home-assistant` folder.
+      4. Right-click the `.vmx` file and select **Open with** > **Notepad**.
+      5. Under `.encoding`, add a line. Enter `firmware = "efi"`.
+      6. Now continue with the next step to start your VM. 
+         - If you see a message about side channel mitigations, select **OK**.
+         - If you see a message stating that the `.vmdk` file could not be found, in step 3, you likely pasted the folder, not the file. Repeat step 3.

-    After the VM has been created, go to **Settings** > **Options** > **Advanced**. Under **Firmware type** select **UEFI**.

 {% elsif page.installation_type == 'alternative' %}

--- a/source/_includes/integrations/google_client_secret.md
+++ b/source/_includes/integrations/google_client_secret.md
@ -49,6 +49,6 @@ This section explains how to generate a client ID and client secret on
    - Once you have noted these strings, select **OK**.
    - If you need to find these credentials again at any point, then navigate to **APIs & Services** > **Credentials**, and you will see **Home Assistant Credentials** (or whatever you named them in the previous step) under **OAuth 2.0 Client IDs**.
    - To view both the **Client ID** and **Client secret**, select the pencil icon. This will take you to the settings page for these credentials, and the information will be on the right-hand side of the page.
-16. Congratulations! You are now the keeper of a client secret. Guard it in your treasure box.
+16. Congratulations! You are now the keeper of a client secret. Guard it in your treasure box. In most cases your new credentials will be active within a few moments. However, Google states that activation may take up to five hours in some circumstances.

 {% enddetails %}
--- a/source/_integrations/abode.markdown
+++ b/source/_integrations/abode.markdown
@ -30,7 +30,7 @@ ha_platforms:
 ha_integration_type: integration
 ---

-The **Abode** {% term integration %} will allow users to integrate their Abode Home Security systems into Home Assistant and use its alarm system and sensors to automate their homes.
+The **Abode** {% term integration %} allows you to integrate your Abode Home Security systems into Home Assistant and use its alarm system and sensors to trigger automations.

 Please visit the [Abode website](https://goabode.com/) for further information about Abode Security.

--- a/source/_integrations/acmeda.markdown
+++ b/source/_integrations/acmeda.markdown
@ -34,5 +34,5 @@ If the IP address for the hub changes, you will need to re-register it with Home

 The integration has the following limitations:

- covers with position as well as tilt are not supported.
- the integration doesn't make use of rooms and scenes configured in the hub, use the equivalent functionality in Home Assistant instead.
+- Covers with position as well as tilt are not supported.
+- The integration doesn't make use of rooms and scenes configured in the hub, use the equivalent functionality in Home Assistant instead.
--- a/source/_integrations/actiontec.markdown
+++ b/source/_integrations/actiontec.markdown
@ -11,7 +11,7 @@ ha_platforms:
 ha_integration_type: integration
 ---

-The **Actiontec** {% term integration %} allows you to detect presence by looking at connected devices to an [Actiontec](https://www.actiontec.com/) device.
+The **Actiontec** {% term integration %} allows you to detect presence by looking at devices connected to an [Actiontec](https://www.actiontec.com/) device.

 Supported devices (tested):

--- a/source/_integrations/adax.markdown
+++ b/source/_integrations/adax.markdown
@ -14,13 +14,21 @@ ha_platforms:
 ha_integration_type: integration
 ---

-The **Adax** {% term integration %} integrates Adax heater into Home Assistant.
+The **Adax** {% term integration %} integrates Adax heaters into Home Assistant and can be configured to use a local or cloud interface.

-You can configure the heaters to use a local or cloud interface.
+## Local integration

-The local integrations only works with newer Adax heaters with both Bluetooth and wifi. Home Assistant uses Bluetooth LE to configure the heaters, this means your machine running “Home Assistant” needs to have a Bluetooth adapter and the heater needs to be in range during setup. For the local integration, you have to reset the heater by pressing + and OK until the display shows 'Reset'. Then press and hold the OK button on the heater until the blue LED starts blinking before pressing Submit. Configuring the heater might take some minutes. Using the local integration will disable cloud communication and the Adax app will not work.
+The local integration only works with newer Adax heaters with both Bluetooth and Wi-Fi. Home Assistant uses Bluetooth LE to configure the heaters, this means the machine _running_ Home Assistant needs to have a Bluetooth adapter and the heater needs to be in range during setup. Using local control will disable cloud communication and the Adax app will not work.

-For the cloud integration, you'll need the Account ID (which can be found in the Adax Wifi app, pressing 'Account'. Which you will find as a number between the "log out" and "close account" buttons). 
+1. Reset the heater by pressing **+** and **OK** until the display shows **Reset**.
+2. Press and hold the **OK** button on the heater until the blue LED starts blinking.
+3. Press **Submit**.
+
+This process may take several minutes.
+
+## Cloud integration
+
+For the cloud integration, you'll need your Account ID. This can be found in the Adax WiFi app by pressing **Account**. The ID will be shown as a number between the **log out** and **close account** buttons.

 You will also need a credential, which you can create in the Adax app:

--- a/source/_integrations/adguard.markdown
+++ b/source/_integrations/adguard.markdown
@ -17,9 +17,9 @@ ha_platforms:
 ha_integration_type: service
 ---

-AdGuard Home is a network-wide ad- and tracker-blocking DNS server with parental
-control (adult content blocking) capabilities. The **AdGuard** integration allows
-you to control and monitor your AdGuard Home instance in Home Assistant.
+AdGuard Home is a network-wide DNS server that supports ad, tracker,
+and adult content blocking. The **AdGuard** integration allows you to control and
+monitor your AdGuard Home instance in Home Assistant.

 {% include integrations/config_flow.md %}

--- a/source/_integrations/agent_dvr.markdown
+++ b/source/_integrations/agent_dvr.markdown
@ -16,7 +16,7 @@ ha_platforms:
 ha_integration_type: integration
 ---

-[Agent DVR](https://www.ispyconnect.com/download.aspx/) is a free* software DVR solution for windows 10, Mac and Linux. Agent DVR runs as a service or console application and can access and control a huge range of third party cameras with advanced motion detection, including DeepStack integration for object recognition. The iSpyConnect website provides secured (SSL) remote access without port forwarding needed.
+[Agent DVR](https://www.ispyconnect.com/download.aspx/) is a free* software DVR solution for Windows 10, Mac and Linux. Agent DVR runs as a service or console application and can access and control a huge range of third party cameras with advanced motion detection, including DeepStack integration for object recognition. The iSpyConnect website provides secured (SSL) remote access without port forwarding needed.

 You can add Agent DVR via integrations using the IP address and port of the server, e.g.,: `http://192.168.1.3:8090/`.

@ -63,7 +63,7 @@ Service data attribute | Optional | Description
 -|-|-
 `entity_id` | no | Name(s) of entities, e.g., `camera.living_room_camera`.

-## IFrame
+## Iframe

 - Using the Webpage Card you can embed the Agent DVR viewer directly in Home Assistant. Just point it to <https://www.ispyconnect.com/app/>

--- a/source/_integrations/alert.markdown
+++ b/source/_integrations/alert.markdown
@ -32,7 +32,7 @@ State | Description
 ### Basic example

 The `alert` integration makes use of any of the `notification` integrations. To
-setup the `alert` integration, first, you must setup a `notification` integration.
+setup the `alert` integration, first, you must set up a [notification integration](/integrations/#notifications).
 Then, add the following to your configuration file:

 ```yaml
--- a/source/_integrations/apcupsd.markdown
+++ b/source/_integrations/apcupsd.markdown
@ -15,6 +15,7 @@ ha_platforms:
  - binary_sensor
  - sensor
 ha_integration_type: integration
+ha_quality_scale: silver
 ---

 [apcupsd](http://www.apcupsd.org/) status information can be integrated into Home Assistant when the Network Information Server (NIS) [is configured](http://www.apcupsd.org/manual/manual.html#nis-server-client-configuration-using-the-net-driver) on the APC device.
--- a/source/_integrations/blink.markdown
+++ b/source/_integrations/blink.markdown
@ -11,13 +11,16 @@ ha_release: '0.40'
 ha_iot_class: Cloud Polling
 ha_codeowners:
  - '@fronzbot'
+  - '@mkmer'
 ha_domain: blink
 ha_config_flow: true
 ha_platforms:
  - alarm_control_panel
  - binary_sensor
  - camera
+  - diagnostics
  - sensor
+  - switch
 ha_dhcp: true
 ha_integration_type: integration
 ---
--- a/source/_integrations/brandt.markdown
+++ b/source/_integrations/brandt.markdown
@ -44,7 +44,7 @@ ha_platforms:
  - siren
  - switch
  - water_heater
-ha_iot_class: Cloud Polling
+ha_iot_class: Local Polling
 ha_dhcp: true
 ha_zeroconf: true
 ---
--- a/source/_integrations/broadlink.markdown
+++ b/source/_integrations/broadlink.markdown
@ -17,6 +17,7 @@ ha_codeowners:
 ha_domain: broadlink
 ha_config_flow: true
 ha_platforms:
+  - climate
  - light
  - remote
  - sensor
--- a/source/_integrations/caldav.markdown
+++ b/source/_integrations/caldav.markdown
@ -11,6 +11,7 @@ ha_platforms:
  - calendar
  - todo
 ha_integration_type: integration
+ha_config_flow: true
 ---

 The CalDAV integration allows you to connect your WebDAV calendar to Home Assistant
@ -196,4 +197,4 @@ You may be required to use [app specific passwords](https://support.apple.com/en
 to generate a new password for use by Home Assistant to avoid sharing your iCloud account
 password.

-{% enddetails %}
+{% enddetails %}
--- a/source/_integrations/cozytouch.markdown
+++ b/source/_integrations/cozytouch.markdown
@ -44,7 +44,7 @@ ha_platforms:
  - siren
  - switch
  - water_heater
-ha_iot_class: Cloud Polling
+ha_iot_class: Local Polling
 ha_dhcp: true
 ha_zeroconf: true
 ---
--- a/source/_integrations/cups.markdown
+++ b/source/_integrations/cups.markdown
@ -13,7 +13,7 @@ ha_platforms:
 ha_integration_type: integration
 ---

-The `cups` sensor platform is using the open source printing system [CUPS](https://www.cups.org/) to show details about your printers, including the ink levels. It can obtain the information using a CUPS server or communicating directly with the printer with the Internet Printing Protocol.
+The `cups` sensor platform uses the open source printing system [CUPS](https://www.cups.org/) to show details about your printers, including the ink levels. It can obtain the information using a CUPS server or by communicating directly with the printer with the Internet Printing Protocol.

 ## Setup

@ -40,7 +40,7 @@ sensor:

 {% configuration %}
 printers:
-  description: List of printers to add. If you're not using a CUPS server, add here your "Printer Name".
+  description: List of printers to add. If you're not using a CUPS server, add your "Printer Name" here.
  required: true
  type: list
 host:
@ -73,9 +73,3 @@ sensor:
    printers:
      - ipp/print
 ```
-
-<div class='note'>
-
-You will need to install the `python3-dev` or `python3-devel` and the development files for CUPS (`libcups2-dev` or`cups-devel`) package on your system manually (eg. `sudo apt-get install python3-dev libcups2-dev` or `sudo dnf -y install python3-devel cups-devel`) along with a compiler (`gcc`).
-
-</div>
--- a/source/_integrations/debugpy.markdown
+++ b/source/_integrations/debugpy.markdown
@ -1,5 +1,5 @@
 ---
-title: Remote Python debugger
+title: Remote Python Debugger
 description: Remote Python debugger (debugpy) for Visual Studio Code
 ha_category:
  - Utility
--- a/source/_integrations/decora_wifi.markdown
+++ b/source/_integrations/decora_wifi.markdown
@ -40,4 +40,3 @@ password:
  required: true
  type: string
 {% endconfiguration %}
-
--- a/source/_integrations/devialet.markdown
+++ b/source/_integrations/devialet.markdown
@ -8,12 +8,12 @@ ha_iot_class: Local Polling
 ha_config_flow: true
 ha_domain: devialet
 ha_codeowners:
-  - '@westenbergf'
-ha_zeroconf:
+  - '@fwestenberg'
+ha_zeroconf: true
+ha_integration_type: device
+ha_platforms:
  - diagnostics
  - media_player
-ha_zeroconf: true
-ha_integration_type: integration
 ---

 The **Devialet** integration lets you control your [Devialet](https://www.devialet.com) wireless speakers from Home Assistant.
--- a/source/_integrations/dwd_weather_warnings.markdown
+++ b/source/_integrations/dwd_weather_warnings.markdown
@ -13,7 +13,7 @@ ha_codeowners:
  - '@andarotajo'
 ha_platforms:
  - sensor
-ha_integration_type: integration
+ha_integration_type: service
 ---

 The **Deutscher Wetterdienst Weather Warnings** {% term integration %} uses the [Deutscher Wetterdienst (DWD)](https://www.dwd.de) as a source for current and advance weather warnings. The configured sensor checks for data every 15 minutes.
--- a/source/_integrations/ecobee.markdown
+++ b/source/_integrations/ecobee.markdown
@ -14,7 +14,6 @@ ha_release: 0.9
 ha_iot_class: Cloud Polling
 ha_config_flow: true
 ha_codeowners:
-  - '@marthoc'
  - '@marcolivierarsenault'
 ha_domain: ecobee
 ha_platforms:
--- a/source/_integrations/econet.markdown
+++ b/source/_integrations/econet.markdown
@ -10,7 +10,6 @@ ha_release: 0.61
 ha_iot_class: Cloud Push
 ha_domain: econet
 ha_codeowners:
-  - '@vangorra'
  - '@w1ll1am23'
 ha_config_flow: true
 ha_platforms:
--- a/source/_integrations/enphase_envoy.markdown
+++ b/source/_integrations/enphase_envoy.markdown
@ -13,6 +13,7 @@ ha_codeowners:
  - '@cgarwood'
  - '@dgomes'
  - '@joostlek'
+  - '@catsmanac'
 ha_platforms:
  - binary_sensor
  - diagnostics
--- a/source/_integrations/envisalink.markdown
+++ b/source/_integrations/envisalink.markdown
@ -13,8 +13,6 @@ ha_platforms:
  - binary_sensor
  - sensor
  - switch
-ha_codeowners:
-  - '@ufodone'
 ha_integration_type: integration
 ---

--- a/source/_integrations/ezviz.markdown
+++ b/source/_integrations/ezviz.markdown
@ -169,4 +169,4 @@ The image entity represents the last detected event from a camera and visually r

 ## Related topics

- [Controlling the camera from the dashboard](/dashboards/picture-glance/#creating-a-card-to-control-the-camera)
+- [Controlling the camera from the dashboard](/dashboards/picture-glance/#creating-a-card-to-control-the-camera)
--- a/source/_integrations/fastdotcom.markdown
+++ b/source/_integrations/fastdotcom.markdown
@ -35,4 +35,4 @@ By default, a speed test will be run every hour. The user can manually run a spe

 - When running on Raspberry Pi 3 or older, the maximum speed is limited by its 100 Mbit/s LAN adapter.
 - The sensor will return the maximum measured speed during a 15-second test.
- Speed tests consume data depending on your internet speed. Make sure to consider this if your internet connection has limited bandwidth.
+- Speed tests consume data depending on your internet speed. Make sure to consider this if your internet connection has limited bandwidth.
--- a/source/_integrations/fints.markdown
+++ b/source/_integrations/fints.markdown
@ -8,7 +8,7 @@ ha_iot_class: Cloud Polling
 ha_domain: fints
 ha_platforms:
  - sensor
-ha_integration_type: integration
+ha_integration_type: service
 ---

 With the FinTS sensor, you can fetch your account information from your bank. This only works with banks that support the FinTS (aka. HBCI) standard. The FinTS standard used by many German banks. So if you do not have a German bank account, this will most likely not work for you. To find out if your bank supports FinTS, check the bank's website or call their hotline.
--- a/source/_integrations/flexom.markdown
+++ b/source/_integrations/flexom.markdown
@ -44,7 +44,7 @@ ha_platforms:
  - siren
  - switch
  - water_heater
-ha_iot_class: Cloud Polling
+ha_iot_class: Local Polling
 ha_dhcp: true
 ha_zeroconf: true
 ---
--- a/source/_integrations/freebox.markdown
+++ b/source/_integrations/freebox.markdown
@ -2,12 +2,12 @@
 title: Freebox
 description: Instructions on how to integrate Freebox routers into Home Assistant.
 ha_category:
+  - Alarm Control Panel
  - Camera
  - Network
  - Presence detection
  - Sensor
  - Switch
-  - Alarm Control Panel
 ha_release: 0.85
 ha_iot_class: Local Polling
 ha_codeowners:
@ -16,13 +16,13 @@ ha_codeowners:
 ha_config_flow: true
 ha_domain: freebox
 ha_platforms:
+  - alarm_control_panel
  - binary_sensor
  - button
  - camera
  - device_tracker
  - sensor
  - switch
-  - alarm_control_panel
 ha_zeroconf: true
 ha_integration_type: integration
 ---
--- a/source/_integrations/google_assistant.markdown
+++ b/source/_integrations/google_assistant.markdown
@ -363,7 +363,7 @@ If you receive 404 errors linked to reporting state in your log, Home Assistant

 #### Error during linking: "Could not update the setting. Please check your connection"

-Your fulfillment URL may be invalid or unreachable. Recheck the `Fulfillment URL` as specified in [Manual Setup](#manual-setup) and verify that it's publicly reachable.
+Your fulfillment URL may be invalid or unreachable. Recheck the `Fulfillment URL` as specified in [Manual Setup](#manual-setup-if-you-dont-have-home-assistant-cloud) and verify that it's publicly reachable.

 #### 500 / 429 error on request sync

--- a/source/_integrations/growatt_server.markdown
+++ b/source/_integrations/growatt_server.markdown
@ -6,8 +6,6 @@ ha_category:
  - Sensor
 ha_release: 0.99
 ha_iot_class: Cloud Polling
-ha_codeowners:
-  - '@muppet3000'
 ha_domain: growatt_server
 ha_platforms:
  - sensor
--- a/source/_integrations/hexaom.markdown
+++ b/source/_integrations/hexaom.markdown
@ -44,7 +44,7 @@ ha_platforms:
  - siren
  - switch
  - water_heater
-ha_iot_class: Cloud Polling
+ha_iot_class: Local Polling
 ha_dhcp: true
 ha_zeroconf: true
 ---
--- a/source/_integrations/hi_kumo.markdown
+++ b/source/_integrations/hi_kumo.markdown
@ -44,7 +44,7 @@ ha_platforms:
  - siren
  - switch
  - water_heater
-ha_iot_class: Cloud Polling
+ha_iot_class: Local Polling
 ha_dhcp: true
 ha_zeroconf: true
 ---
--- a/source/_integrations/idasen_desk.markdown
+++ b/source/_integrations/idasen_desk.markdown
@ -12,9 +12,11 @@ ha_bluetooth: true
 ha_platforms:
  - button
  - cover
+  - sensor
 ha_integration_type: integration
 ha_codeowners:
  - '@abmantis'
+ha_quality_scale: silver
 ---

 The IKEA IDÅSEN integration allows you to connect your IKEA Idåsen motorized desk to Home Assistant, making it possible to control the desk height and also monitor height changes from the physical controller.
@ -49,4 +51,3 @@ Height:
  description: The current height of the desk, in meters.

 {% endconfiguration_basic %}
-
--- a/source/_integrations/light.mqtt.markdown
+++ b/source/_integrations/light.mqtt.markdown
@ -711,7 +711,7 @@ state_topic:
  required: false
  type: string
 supported_color_modes:
-  description: A list of color modes supported by the list. This is required if `color_mode` is `True`. Possible color modes are `onoff`, `brightness`, `color_temp`, `hs`, `xy`, `rgb`, `rgbw`, `rgbww`, `white`.
+  description: A list of color modes supported by the list. This is required if `color_mode` is `True`. Possible color modes are `onoff`, `brightness`, `color_temp`, `hs`, `xy`, `rgb`, `rgbw`, `rgbww`, `white`. Note that if `onoff` **or** `brightness` are used, that must be the _only_ value in the list.
  required: false
  type: list
 unique_id:
--- a/source/_integrations/linear_garage_door.markdown
+++ b/source/_integrations/linear_garage_door.markdown
@ -1,15 +1,18 @@
 ---
-title: "Linear garage door"
-description: "Control Linear garage doors"
-ha_release: "2023.12"
+title: Linear Garage Door
+description: Control Linear garage doors
+ha_release: '2023.12'
 ha_category:
  - Cover
-ha_iot_class: "Cloud Polling"
-ha_quality_scale: gold
+ha_iot_class: Cloud Polling
 ha_config_flow: true
 ha_codeowners:
  - '@IceBotYT'
 ha_domain: linear_garage_door
+ha_platforms:
+  - cover
+  - diagnostics
+ha_integration_type: integration
 ---

 The Linear integration lets you control Linear garage doors through Home Assistant. Device names in Home Assistant are generated based on the names defined in your Linear mobile app.
--- a/source/_integrations/litejet.markdown
+++ b/source/_integrations/litejet.markdown
@ -24,7 +24,7 @@ LiteJet is a centralized lighting system that predates most home automation tech

 ## Prerequisites

-Your LiteJet MCP should be configured for 19.2 K baud, 8 data bits, 1 stop bit, no parity, and to transmit a 'CR' after each response. These settings can be configured using the [LiteJet programming software](https://www.centralite.com/helpdesk/knowledgebase.php?article=735). Connect the LiteJet's RS232-2 port to your computer.
+Your LiteJet MCP should be configured for 19.2 K baud, 8 data bits, 1 stop bit, no parity, and to transmit a 'CR' after each response. These settings can be configured using the LiteJet programming software from the [Dragon Technologies](https://www.dragontechinc.com/) Programming page. Connect the LiteJet's RS232-2 port to your computer.

 {% include integrations/config_flow.md %}

--- a/source/_integrations/moehlenhoff_alpha2.markdown
+++ b/source/_integrations/moehlenhoff_alpha2.markdown
@ -18,7 +18,7 @@ ha_integration_type: integration
 ---

 The Möhlenhoff Alpha 2 integration allows you to control a
-[Möhlenhoff Alpha 2](https://www.moehlenhoff.de/en/products/room-by-room-control/oem-alpha-2-system)
+[Möhlenhoff Alpha 2](https://www.moehlenhoff.de/fileadmin/user_upload/Download/Broschueren/125297_1705_Broschuere_Alpha2_DEU_final_web.pdf)
 temperature control system.

 ## Prerequisites
--- a/source/_integrations/mqtt.markdown
+++ b/source/_integrations/mqtt.markdown
@ -685,6 +685,7 @@ The following software has built-in support for MQTT discovery:
 - [EMS-ESP32 (and EMS-ESP)](https://github.com/emsesp/EMS-ESP32)
 - [ESPHome](https://esphome.io)
 - [ESPurna](https://github.com/xoseperez/espurna)
+- [go-iotdevice](https://github.com/koestler/go-iotdevice)
 - [HASS.Agent](https://github.com/LAB02-Research/HASS.Agent)
 - [IOTLink](https://iotlink.gitlab.io) (starting with 2.0.0)
 - [MiFlora MQTT Daemon](https://github.com/ThomDietrich/miflora-mqtt-daemon)
@ -843,7 +844,7 @@ Setting up a light, switch etc. is similar but requires a `command_topic` as men

 ```bash
 mosquitto_pub -r -h 127.0.0.1 -p 1883 -t "homeassistant/switch/irrigation/config" \
-  -m '{"name": "Irrigation", "command_topic": "homeassistant/switch/irrigation/set", "state_topic": "homeassistant/switch/irrigation/state", "unique_id": "irr01ad", "device": {"identifiers": ["garden01ad"], "name": "Garden" }}}'
+  -m '{"name": "Irrigation", "command_topic": "homeassistant/switch/irrigation/set", "state_topic": "homeassistant/switch/irrigation/state", "unique_id": "irr01ad", "device": {"identifiers": ["garden01ad"], "name": "Garden" }}'
 ```

 Set the state:
--- a/source/_integrations/namecheapdns.markdown
+++ b/source/_integrations/namecheapdns.markdown
@ -9,10 +9,10 @@ ha_domain: namecheapdns
 ha_integration_type: integration
 ---

-With the `namecheapdns` integration you can automatically update your dynamic DNS entry at [namecheapdns](https://www.namecheap.com/store/domains/freedns/).
+With the `namecheapdns` integration you can automatically update your dynamic DNS entry hosted by Namecheap's [FreeDNS](https://www.namecheap.com/store/domains/freedns/) service.

 <div class='note warning'>
-Namecheap only supports IPv4 addresses to update.
+Namecheap only supports updating IPv4 addresses.
 </div>

 ## Configuration
@ -32,13 +32,13 @@ namecheapdns:
    required: false
    type: string
  domain:
-    description: Your namecheap TLD (example.com).
+    description: Your root domain (example.com).
    required: true
    type: string
  password:
-    description: The namecheap "Dynamic DNS Password" you can find under the "Advanced DNS" tab.
+    description: The Namecheap "Dynamic DNS Password" you can find under the "Advanced DNS" tab.
    required: true
    type: string
 {% endconfiguration %}

-See the [How do I set up a Host for Dynamic DNS?](https://www.namecheap.com/support/knowledgebase/article.aspx/43/11/how-do-i-set-up-a-host-for-dynamic-dns) for further instructions
+See Namecheap's [How do I set up a Host for Dynamic DNS?](https://www.namecheap.com/support/knowledgebase/article.aspx/43/11/how-do-i-set-up-a-host-for-dynamic-dns) guide for further instructions.
--- a/source/_integrations/nest.markdown
+++ b/source/_integrations/nest.markdown
@ -533,6 +533,8 @@ authentication process.

 - *Something went wrong: Please contact the developer of this app if the issue persists*: This typically means you are using the wrong type of credential (e.g. *Desktop Auth*). Make sure the credential in the [Google Cloud Console](https://console.developers.google.com/apis/credentials) is a *Web Application* credential following the instructions above.

+- *Something went wrong, please try again in a few minutes*: According to Google's [Partner Connections Manager Error Reference](https://developers.google.com/nest/device-access/reference/errors/pcm), this error covers all other undocumented internal errors within Partner Connections. One of the issues that cause this error is synchronization problems between the Nest and Google Home apps. Confirm that your Nest device is visible within both apps under the same Home. If it is missing within Google Home, create a new dummy home on the Nest app, which triggers the synchronization process. (This is the workaround recommended by the Google support team). The dummy entry can be deleted once the Nest device is visible within the Google Home app.
+
 - *Can’t link to [Project Name]: Please contact [Project Name] if the issue persists*: This typically means that the *OAuth Client ID* used is mismatched

 {% details "Resolving mismatched OAuth Client ID" %}
--- a/source/_integrations/nexity.markdown
+++ b/source/_integrations/nexity.markdown
@ -44,7 +44,7 @@ ha_platforms:
  - siren
  - switch
  - water_heater
-ha_iot_class: Cloud Polling
+ha_iot_class: Local Polling
 ha_dhcp: true
 ha_zeroconf: true
 ---
--- a/source/_integrations/nobo_hub.markdown
+++ b/source/_integrations/nobo_hub.markdown
@ -14,7 +14,7 @@ ha_platforms:
  - climate
  - select
  - sensor
-ha_integration_type: integration
+ha_integration_type: hub
 ---

 Integrates [Nobø Ecohub](https://www.glendimplex.no/produkter/varmestyring/11123610/noboe-hub/c-77/p-330)
--- a/source/_integrations/notify.tts.markdown
+++ b/source/_integrations/notify.tts.markdown
@ -25,8 +25,6 @@ notify:
    media_player: media_player.living_room
 ```

-Please note that the `tts_service` parameter, must match the `service_name` defined in the TTS integration.
-
 {% configuration %}
  name:
    description: The name of the notify service.
--- a/source/_integrations/openai_conversation.markdown
+++ b/source/_integrations/openai_conversation.markdown
@ -35,7 +35,7 @@ Prompt Template:
  description: The starting text for the AI language model to generate new text from. This text can include information about your Home Assistant instance, devices, and areas and is written using [Home Assistant Templating](/docs/configuration/templating/).

 Completion Model:
-  description: The GPT-3 language model is used for text generation. You can find more details on the available models in the [OpenAI GPT-3 Documentation](https://platform.openai.com/docs/models/gpt-3).
+  description: The GPT language model is used for text generation. You can find more details on the available models in the [OpenAI GPT-3 Documentation](https://platform.openai.com/docs/models/gpt-3), [OpenAI GPT-3.5 Documentation](https://platform.openai.com/docs/models/gpt-3-5), or [OpenAI GPT-4 and GPT-4 Turbo Documentation](https://platform.openai.com/docs/models/gpt-4-and-gpt-4-turbo). The default is "gpt-3.5-turbo".

 Maximum Tokens to Return in Response:
  description: The maximum number of words or "tokens" that the AI model should generate in its completion of the prompt. For more information, see the [OpenAI Completion Documentation](https://platform.openai.com/docs/guides/completion/introduction).
--- a/source/_integrations/overkiz.markdown
+++ b/source/_integrations/overkiz.markdown
@ -125,4 +125,4 @@ If your hub (e.g. Somfy Connectivity Kit) supports HomeKit natively, your setup

 #### Local API via Velux KLF200 hub

-If you are only using Somfy IO-compatible devices, you could purchase a Velux KLF200 hub and use [the Velux integration](/integrations/velux/) which has a local API. 
+If you are only using Somfy IO-compatible devices, you could purchase a Velux KLF200 hub and use [the Velux integration](/integrations/velux/) which has a local API.
--- a/source/_integrations/philips_js.markdown
+++ b/source/_integrations/philips_js.markdown
@ -2,10 +2,10 @@
 title: Philips TV
 description: Instructions on how to add Philips TVs to Home Assistant.
 ha_category:
+  - Binary sensor
  - Light
  - Media player
  - Remote
-  - Binary sensor
 ha_iot_class: Local Polling
 ha_release: 0.34
 ha_codeowners:
@ -13,12 +13,12 @@ ha_codeowners:
 ha_domain: philips_js
 ha_config_flow: true
 ha_platforms:
+  - binary_sensor
  - diagnostics
  - light
  - media_player
  - remote
  - switch
-  - binary_sensor
 ha_integration_type: integration
 ---

--- a/source/_integrations/picnic.markdown
+++ b/source/_integrations/picnic.markdown
@ -11,6 +11,7 @@ ha_codeowners:
 ha_domain: picnic
 ha_platforms:
  - sensor
+  - todo
 ha_integration_type: integration
 ---

--- a/source/_integrations/piper.markdown
+++ b/source/_integrations/piper.markdown
@ -15,6 +15,7 @@ ha_config_flow: true
 ha_platforms:
  - stt
  - tts
+  - wake_word
 ha_iot_class: Local Push
 ---

--- a/source/_integrations/proximity.markdown
+++ b/source/_integrations/proximity.markdown
@ -9,6 +9,8 @@ ha_quality_scale: internal
 ha_domain: proximity
 ha_iot_class: Calculated
 ha_integration_type: integration
+ha_codeowners:
+  - '@mib1185'
 ---

 The `proximity` integration allows you to monitor the proximity of devices or persons to a particular [zone](/integrations/zone/) and the direction of travel. The result is an entity created in Home Assistant which maintains the proximity data.
--- a/source/_integrations/prusalink.markdown
+++ b/source/_integrations/prusalink.markdown
@ -32,4 +32,4 @@ To obtain the host name and API key/password:

 ## Related topics

- [PrusaLink documentation](https://help.prusa3d.com/article/prusa-connect-and-prusalink-explained_302608)
+- [PrusaLink documentation](https://help.prusa3d.com/article/prusa-connect-and-prusalink-explained_302608)
--- a/source/_integrations/reolink.markdown
+++ b/source/_integrations/reolink.markdown
@ -14,6 +14,7 @@ ha_platforms:
  - binary_sensor
  - button
  - camera
+  - diagnostics
  - light
  - number
  - select
@ -174,6 +175,13 @@ Depending on the supported features of the camera, switch entities are added for

 For NVRs, a global switch for **Record**, **Push**, **Buzzer**, **Email**, and **FTP** will be available under the NVR device as well as a switch per channel of the NVR under the camera device. The respective feature will only be active for a given channel if both the global and that channel switch are enabled (as is also the case in the Reolink app/client).

+**Push** notifications to a phone will only be provided if the following conditions are met: 
+- The **Push notifications** switch in Home Assistant is ON. 
+- For NVRs,  both the global and channel switch are ON.
+- The Push-notification in the Reolink App of that phone is ON.
+
+The Push-notification in the Reolink app is independent of the Home Assistant setting. It is also independent of the settings on other phones connected to the same camera. Reolink does this so you have an independent way of turning off push notifications per phone.
+
 ## Light entities

 Depending on the supported features of the camera, light entities are added for:
--- a/source/_integrations/repetier.markdown
+++ b/source/_integrations/repetier.markdown
@ -7,7 +7,6 @@ ha_category:
 ha_release: 0.94
 ha_iot_class: Local Polling
 ha_codeowners:
-  - '@MTrab'
  - '@ShadowBr0ther'
 ha_domain: repetier
 ha_platforms:
--- a/source/_integrations/rexel.markdown
+++ b/source/_integrations/rexel.markdown
@ -44,7 +44,7 @@ ha_platforms:
  - siren
  - switch
  - water_heater
-ha_iot_class: Cloud Polling
+ha_iot_class: Local Polling
 ha_dhcp: true
 ha_zeroconf: true
 ---
--- a/source/_integrations/ring.markdown
+++ b/source/_integrations/ring.markdown
@ -16,11 +16,14 @@ ha_dhcp: true
 ha_platforms:
  - binary_sensor
  - camera
+  - diagnostics
  - light
  - sensor
  - siren
  - switch
 ha_integration_type: integration
+ha_codeowners:
+  - '@sdb9696'
 ---

 The Ring integration allows you to integrate your [Ring.com](https://ring.com/) devices in Home Assistant. Due to recent authentication changes of Ring, you will need to run at least Home Assistant 0.104.
--- a/source/_integrations/roborock.markdown
+++ b/source/_integrations/roborock.markdown
@ -21,8 +21,8 @@ ha_domain: roborock
 ha_platforms:
  - binary_sensor
  - button
-  - image
  - diagnostics
+  - image
  - number
  - select
  - sensor
--- a/source/_integrations/roon.markdown
+++ b/source/_integrations/roon.markdown
@ -117,4 +117,3 @@ action:
 mode: queued

 ```
-
--- a/source/_integrations/schlage.markdown
+++ b/source/_integrations/schlage.markdown
@ -12,6 +12,7 @@ ha_codeowners:
  - '@dknowles2'
 ha_platforms:
  - binary_sensor
+  - diagnostics
  - lock
  - sensor
  - switch
--- a/source/_integrations/sensor.rest.markdown
+++ b/source/_integrations/sensor.rest.markdown
@ -411,7 +411,7 @@ rest:

 {% endraw %}

-The example below shows how to extract multiple values from a dictionary from the XML file of a Steamist Steambath Wi-Fi interface. The values are used to create a switch and multiple sensors without having to poll the endpoint numerous times.
+The example below shows how to extract multiple values from a dictionary from the XML file of a Steamist Steambath Wi-Fi interface. The values are used to create multiple sensors without having to poll the endpoint numerous times.

 {% raw %}

@ -431,32 +431,6 @@ rest:
        value_template: "{{ json_value['response']['time0'] }}"
        unit_of_measurement: "minutes"

-    switch:
-      - name: "Steam"
-        value_template: "{{ json_value['response']['usr0'] | int >= 1 }}"
-        turn_on:
-          - service: rest_command.set_steam_led
-            data:
-               led: 6
-          - service: homeassistant.update_entity
-            target:
-               entity_id: sensor.steam_system_data
-          - delay: 00:00:15
-          - service: homeassistant.update_entity
-            target:
-               entity_id: sensor.steam_system_data
-        turn_off:
-          - service: rest_command.set_steam_led
-            data:
-               led: 7
-          - service: homeassistant.update_entity
-            target:
-               entity_id: sensor.steam_system_data
-          - delay: 00:00:15
-          - service: homeassistant.update_entity
-            target:
-               entity_id: sensor.steam_system_data
-
 rest_command:  
  set_steam_led:
    url: http://192.168.1.105/leds.cgi?led={{ led }}
--- a/source/_integrations/simu.markdown
+++ b/source/_integrations/simu.markdown
@ -44,7 +44,7 @@ ha_platforms:
  - siren
  - switch
  - water_heater
-ha_iot_class: Cloud Polling
+ha_iot_class: Local Polling
 ha_dhcp: true
 ha_zeroconf: true
 ---
--- a/source/_integrations/slack.markdown
+++ b/source/_integrations/slack.markdown
@ -119,7 +119,7 @@ sequence:
 mode: single
 ```

-Update the blocks array with valid Slack blocks. The easiest way to create this is using [Slack Block Kit Builder](https://app.slack.com/block-kit-builder)
+Update the blocks array with valid Slack blocks. The easiest way to create this is using [Slack Block Kit Builder](https://app.slack.com/block-kit-builder).  Up to 50 blocks may be included per message.

 Create a duplicate of this script to use for different messages, and different channels (the door was opened in #security, the light was left on on #lights, etc).

@ -142,7 +142,7 @@ The following attributes can be placed inside the `data` key of the service call
 | `username`               |      yes | The username of the Slack bot.
 | `icon`                   |      yes | The icon of the Slack bot.
 | `file`                   |      yes | A file to include with the message; see below.
-| `blocks`                 |      yes | Array of [Slack blocks](https://api.slack.com/messaging/composing/layouts). *NOTE*: if using `blocks`, they are shown **in place of** the `message` (note that the `message` is required nonetheless).
+| `blocks`                 |      yes | Array of [Slack blocks](https://api.slack.com/messaging/composing/layouts). *NOTE*: if using `blocks`, they are shown **in place of** the `message` within Slack apps. The message field will be used as notification text and anywhere else Slack is unable to display blocks. `message` is required regardless of whether this field is used.
 | `blocks_template`        |      yes | The same as `blocks`, but able to support [templates](https://www.home-assistant.io/docs/configuration/templating).
 | `thread_ts`              |      yes | Sends the message as a reply to a specified parent message.

@ -162,6 +162,16 @@ To include a remote file with the Slack message, use these attributes underneath
 | `username`               |      yes | An optional username if the URL is protected by HTTP Basic Auth.
 | `password`               |      yes | An optional password if the URL is protected by HTTP Basic Auth.

+### Obtaining a member ID
+
+Some of the examples below use a member ID. This is a unique string assigned by Slack to all users (members and guests) and not a username set by the user. To get a member ID:
+
+1. Select a Slack user (both name and profile image work) to bring up their profile side panel.
+2. Open the context menu by selecting the three dots.
+3. Select **Copy member ID**.
+
+![](/images/integrations/slack/slack-member-id.png)
+
 ### Examples

 To send a file from local path:
@ -199,7 +209,7 @@ data:
 To use the block framework:

 ```yaml
-message: Fallback message in case the blocks don't display anything.
+message: Fallback message for notifications or in case the blocks don't display anything.
 title: Title of the file.
 data:
  blocks:
@ -227,7 +237,9 @@ data:
          1.0
 ```

-Send a message directly to a user by setting the target to their member ID. Here are [instructions](https://www.workast.com/help/articles/61000165203/) to obtain a member ID.
+
+Send a message directly to a user by setting the target to their member ID.
+

 ```yaml
 message: "Hello there!"
@ -237,10 +249,10 @@ data:
  blocks: []
 ```

-Send a message to a channel that mentions (@username, highlights a users name in yellow) a user. Here are [instructions](https://www.workast.com/help/articles/61000165203/) to obtain a member ID.
+Send a message to a channel that mentions (@username, highlights a users name in yellow) a user.

 ```yaml
-message: "<@U12345> your appointment starts soon"
+message: "<@MEMBER_ID> your appointment starts soon"
 target: "#general"
 title: "Reminder"
 data:
--- a/source/_integrations/smartthings.markdown
+++ b/source/_integrations/smartthings.markdown
@ -49,7 +49,7 @@ SmartThings is integrated into Home Assistant through the SmartThings Cloud API.

 The PAT is used to create a Home Assistant SmartApp in your SmartThings account during setup of the integration.

-1. Log into the [personal access tokens page](https://account.smartthings.com/tokens) and click '[Generate new token](https://account.smartthings.com/tokens/new)'
+1. Log into the [personal access tokens page](https://account.smartthings.com/tokens) and select **[Generate new token](https://account.smartthings.com/tokens/new)**.
 2. Enter a token name (can be whatever you want), for example, 'Home Assistant' and select the following authorized scopes:
    - Devices (all)
    - Installed Applications (all)
@ -57,7 +57,7 @@ The PAT is used to create a Home Assistant SmartApp in your SmartThings account
    - Locations (all)
    - Scenes (all)
    - Schedules (all)
-3. Click 'Generate token'. When the token is displayed copy and save it somewhere safe (such as your keystore) as you will not be able to retrieve it again.
+3. Select **Generate token**. When the token is displayed copy and save it somewhere safe (such as your keystore) as you will not be able to retrieve it again.

 ### Webhook

@ -72,15 +72,15 @@ After completing the prerequisite steps above, you are ready to setup the integr

 {% include integrations/config_flow.md %}

-1. Confirm the callback URL is correct. If using Home Assistant Cloud, it will start with `https://hooks.nabuca.casa`. If the URL is not correct, update your Home Assistant configuration, restart, and try again.
+1. Confirm the callback URL is correct. If using Home Assistant Cloud, it will start with `https://hooks.nabu.casa`. If the URL is not correct, update your Home Assistant configuration, restart, and try again.
 2. Enter your Personal Access Token.
 3. Select the SmartThings Location to add to Home Assistant.
 4. On the window that opens:
   1. Login with your SmartThings account (if not already logged in).
-   2. Optionally change the display name and click 'Done' at the bottom of the screen.
-   3. Authorize the integration by clicking 'Allow' on the bottom right of the screen.
-   4. Click 'Close Window' or close it manually.
-5. Back in Home Assistant click 'Finish'.
+   2. Optionally change the display name and select **Done** at the bottom of the screen.
+   3. Authorize the integration by selecting **Allow** on the bottom right of the screen.
+   4. Select **Close Window** or close it manually.
+5. Back in Home Assistant select **Finish**.

 <div class='note info'>

@ -90,7 +90,7 @@ If you want to integrate additional SmartThings accounts or locations, repeat th

 ## Removal instructions

-To remove the integration from Home Assistant, select the instance from the Home Assistant Integrations page and click the trash icon on the upper right corner. Alternatively, you can remove the SmartApp from the location within the SmartThings application. If the Home Assistant instance that setup the integration is no longer running or functioning, you will need to use this [utility to remove the orphaned SmartApps in your SmartThings account](https://pypi.org/project/hass-smartthings-remove/).
+To remove the integration from Home Assistant, select the instance from the Home Assistant Integrations page and select the trash icon on the upper right corner. Alternatively, you can remove the SmartApp from the location within the SmartThings application. If the Home Assistant instance that setup the integration is no longer running or functioning, you will need to use this [utility to remove the orphaned SmartApps in your SmartThings account](https://pypi.org/project/hass-smartthings-remove/).

 ## Events

@ -306,11 +306,11 @@ The personal access token does not match the expected format. Make sure you are
 #### Error: `pysmartthings.errors.APIInvalidGrant: Invalid refresh token:` (after a restore)

 You can fix this by using the SmartThings App to re-grant authorization to the API token you created before. 
-1. Open SmartThings app on your mobile device (not HA)
-2. Select `Automations` from bottom
-3. Select your Home Assistant automation from the list
-4. Click "Done", then click "Allow"
-5. Reload your SmartThings integration from Home Assistant Devices panel
+1. Open SmartThings app on your mobile device (not HA).
+2. Select **Automations** from bottom.
+3. Select your Home Assistant automation from the list.
+4. Select **Done**, then select **Allow**.
+5. Reload your SmartThings integration from Home Assistant Devices panel.

 #### Error: The token is invalid or no longer authorized (not solved by above)

--- a/source/_integrations/smtp.markdown
+++ b/source/_integrations/smtp.markdown
@ -204,13 +204,18 @@ notify:
    sender: "YOUR_USERNAME@gmail.com"
    encryption: starttls
    username: "YOUR_USERNAME@gmail.com"
-    password: "YOUR_PASSWORD"
+    password: "YOUR_APP_PASSWORD"
    recipient:
      - "RECIPIENT_1@example.com"
      - "RECIPIENT_N@example.com"
    sender_name: "SENDER_NAME"
 ```

-Keep in mind that Google has some extra layers of protection that need special attention. By default, the usage by external applications is limited so you will need to visit the [less secure apps](https://myaccount.google.com/lesssecureapps) page and enable it to be able to send e-mails. Be aware that Google will periodically turn it off if it is not used (no e-mail is sent).
+Google has some extra layers of protection that need special attention. You must use [an application-specific password](https://support.google.com/mail/answer/185833) in your notification configuration.

-To avoid having your e-mail notifications broken due to the less secure app's behavior, it is recommended that you enable 2-step verification on your Google account, and use [an application-specific password](https://support.google.com/mail/answer/185833) in your notification configuration.
+If any of the following conditions are met you will not be able to create an app password:
+
+- You do not have 2-step verification enabled on your account.
+- You have 2-step verification enabled but have only added a security key as an authentication mechanism.
+- Your Google account is enrolled in Google's [Advanced Protection Program](https://landing.google.com/advancedprotection/).
+- Your Google account belongs to a Google Workspace that has disabled this feature. Accounts owned by a school, business, or other organization are examples of Google Workspace accounts.
--- a/source/_integrations/somfy.markdown
+++ b/source/_integrations/somfy.markdown
@ -44,7 +44,7 @@ ha_platforms:
  - siren
  - switch
  - water_heater
-ha_iot_class: Cloud Polling
+ha_iot_class: Local Polling
 ha_dhcp: true
 ha_zeroconf: true
 ---
--- a/source/_integrations/stt.markdown
+++ b/source/_integrations/stt.markdown
@ -4,7 +4,6 @@ description: Instructions on how to set up speech-to-text (STT) with Home Assist
 ha_release: '0.102'
 ha_codeowners:
  - '@home-assistant/core'
-  - '@pvizeli'
 ha_domain: stt
 ha_quality_scale: internal
 ha_category: []
--- a/source/_integrations/switch.template.markdown
+++ b/source/_integrations/switch.template.markdown
@ -212,7 +212,7 @@ switch:
  - platform: template
    switches:
      garage:
-        value_template: "{{ is_state('cover.garage_door', 'on') }}"
+        value_template: "{{ is_state('cover.garage_door', 'open') }}"
        turn_on:
          service: cover.open_cover
          target:
@ -242,7 +242,7 @@ switch:
  - platform: template
    switches:
      garage:
-        value_template: "{{ is_state('cover.garage_door', 'on') }}"
+        value_template: "{{ is_state('cover.garage_door', 'open') }}"
        turn_on:
          service: cover.open_cover
          target:
--- a/source/_integrations/synology_dsm.markdown
+++ b/source/_integrations/synology_dsm.markdown
@ -37,20 +37,19 @@ This sensor will wake up your Synology NAS if it's in hibernation mode.

 You can change the scan interval within the configuration options (default is 15 min).

-Having cameras or the Home mode toggle from [Surveillance Station](https://www.synology.com/en-us/surveillance) will fetch every 30 seconds. Disable those entities if you don't want your NAS to be fetch as frequently.
+Having cameras or the Home mode toggle from [Surveillance Station](https://www.synology.com/en-us/surveillance) will fetch every 30 seconds. Disable those entities if you don't want your NAS to be fetched as frequently.

 </div>

 <div class='note'>

-If you have two or more NICs with different IP addresses from the same subnet and SSDP is activated, this leads to problems with this integration, as the NAS is detected several times with different IPs and the integration always adopts the new "detected" IP address in its configuration and then reloads it.
-In this case, it is recommended to use NIC bonding instead or to deactivate SSDP.
+When SSDP is activated on a NAS with two or more NICs with different IP addresses on the same subnet an adoption loop will occur. The NAS will be detected several times with different IP addresses and the integration will adopt the "newly" detected IP causing a reload. To resolve this either <a href="https://kb.synology.com/en-id/DSM/help/DSM/AdminCenter/file_service_advanced_introduction?version=7" target="_blank">deactivate SSDP on the NAS</a> or use NIC bonding so that only one IP address is present.

 </div>

 ## Separate User Configuration

-Due to the nature of the Synology DSM API, it is required to grant the user admin rights. This is related to the fact that utilization information is stored in the core module.
+You must grant the user admin rights in order to access utilization information since it's stored in the core module.

 When creating the user, it is possible to deny access to all locations and applications. By doing this, the user will not be able to login to the web interface or view any of the files on the Synology NAS. It is still able to read the utilization and storage information using the API.

@ -58,9 +57,9 @@ If you want to add cameras from [Surveillance Station](https://www.synology.com/

 ### If you utilize 2-Step Verification or Two Factor Authentication (2FA) with your Synology NAS

-If you have the "Enforce 2-step verification for the following users" option checked under **Control Panel > Security > Account > 2-Factor Authentication**, you'll need to configure the 2-step verification/one-time password (OTP) for the user you just created before the credentials for this user will work with Home Assistant. 
+If you have the "Enforce 2-step verification for the following users" option checked under **Control Panel > Security > Account > 2-Factor Authentication**, you'll need to configure the 2-step verification/one-time password (OTP) for the user you just created before the credentials for this user will work with Home Assistant.

-Make sure to log out of your "normal" user's account and then login with the separate user you created specifically for Home Assistant. DSM will walk you through the process of setting up the one-time password for this user which you'll then be able to use in Home Assistant's frontend configuration screen. 
+Make sure to log out of your "normal" user's account and then login with the separate user you created specifically for Home Assistant. DSM will walk you through the process of setting up the one-time password for this user which you'll then be able to use in Home Assistant's frontend configuration screen.

 <div class='note'>
 If you denied access to all locations and applications it is normal to receive a message indicating you do not have access to DSM when trying to login with this separate user. As noted above, you do not need access to the DSM and Home Assistant will still be able to read statistics from your NAS.
@ -68,15 +67,15 @@ If you denied access to all locations and applications it is normal to receive a

 ## Sensors

-### CPU Utilisation sensors
+### CPU utilization sensors

-Entities reporting the current and combined CPU utilization of the NAS. There are sensors the report the current CPU load, separated by User, System and others. By default, only the User sensor is enabled.
+Entities reporting the current and combined CPU utilization of the NAS. There are sensors that report the current CPU load separated by User, System, and others. By default only the User sensor is enabled.

 There are also combined CPU load sensors. These report the total CPU load for the entire NAS. Available as current, 1min, 5min and 15min load sensors. By default the 1min load sensor is disabled.

-### Memory Utilisation sensors
+### Memory utilization sensors

-Entities reporting the current and combined memory and swap utilization of the NAS. These sensors include the total installed amount, the currently free amount and the % of memory used. 
+Entities reporting the current and combined memory and swap utilization of the NAS. These sensors include the total installed amount, the currently free amount, and the % of memory used.

 ### Network sensors

@ -116,7 +115,7 @@ A switch is available to enable/disable the [Surveillance Station](https://www.s

 ## Cameras

-For each camera added in [Surveillance Station](https://www.synology.com/surveillance), a camera will be created in Home Assistant.
+For each camera added in [Surveillance Station](https://www.synology.com/surveillance) a camera will be created in Home Assistant.

 ## Buttons

@ -134,7 +133,7 @@ A media source is provided for your [Synology Photos](https://www.synology.com/e

 The media source URIs will look like `media-source://synology_dsm/<unique_id>/<album_id>/<image>`.

-This media browser supports multiple Synology Photos instances. `<unique_id>` is the Home Assistant ID for the NAS (_usually the serial number of the NAS_). You can find this id when using the media browser, when you hover over the NAS name, you get shown the simple name followed by the unique id ex: `192.168.0.100:5001 - 18C0PEN253705`. 
+This media browser supports multiple Synology Photos instances. `<unique_id>` is the Home Assistant ID for the NAS (_usually the serial number of the NAS_). You can find this id when using the media browser by hovering over the NAS name. It will show the simple name followed by the unique id ex: `192.168.0.100:5001 - 18C0PEN253705`.

 To find the `<album_id>` you need to go to the album in your photos instance, and the id will be in the URL ex: `https://192.168.0.100:5001/#/album/19`, where 19 is the album id. An `<album_id>` of 0 will contain all images.

--- a/source/_integrations/system_bridge.markdown
+++ b/source/_integrations/system_bridge.markdown
@ -4,6 +4,7 @@ description: How to integrate the System Bridge integration into Home Assistant.
 ha_category:
  - Sensor
  - System monitor
+  - Update
 ha_release: 2021.6
 ha_iot_class: Local Push
 ha_config_flow: true
--- a/source/_integrations/thethingsnetwork.markdown
+++ b/source/_integrations/thethingsnetwork.markdown
@ -16,6 +16,7 @@ ha_integration_type: integration

 <div class='note warning'>
  This integration only supports TTNv2 that has been definitively switched off in 2022 (deprecated).
+  For TTNv3, use the [MQTT integration](/integrations/mqtt).
 </div>

 The `thethingsnetwork` integration allows one to interact with the [The Things Network](https://www.thethingsnetwork.org). This community-driven and open network supports [LoRaWAN](https://www.lora-alliance.org/) for long range (~5 to 15 km) communication with a low bandwidth (51 bytes/message). [Gateways](https://www.thethingsnetwork.org/docs/gateways/) transfers the received data from the sensors to the The Things Network.
--- a/source/_integrations/todo.markdown
+++ b/source/_integrations/todo.markdown
@ -76,6 +76,7 @@ data:
  item: "Submit Income Tax Return"
  due_date: "2024-04-10"
  description: "Collect all necessary documents and submit the final return."
+```

 ### Service `todo.update_item`

@ -130,4 +131,4 @@ This is a full example of a service call that deletes all completed to-do items.
 service: todo.remove_completed_items
 target:
  entity_id: todo.personal_tasks
-```
+```
--- a/source/_integrations/tplink.markdown
+++ b/source/_integrations/tplink.markdown
@ -12,6 +12,7 @@ ha_config_flow: true
 ha_codeowners:
  - '@rytilahti'
  - '@thegardenmonkey'
+  - '@bdraco'
 ha_domain: tplink
 ha_platforms:
  - diagnostics
--- a/source/_integrations/tts.markdown
+++ b/source/_integrations/tts.markdown
@ -7,7 +7,6 @@ ha_category:
 ha_release: 0.35
 ha_codeowners:
  - '@home-assistant/core'
-  - '@pvizeli'
 ha_domain: tts
 ha_quality_scale: internal
 ha_platforms:
--- a/source/_integrations/ubiwizz.markdown
+++ b/source/_integrations/ubiwizz.markdown
@ -44,7 +44,7 @@ ha_platforms:
  - siren
  - switch
  - water_heater
-ha_iot_class: Cloud Polling
+ha_iot_class: Local Polling
 ha_dhcp: true
 ha_zeroconf: true
 ---
--- a/source/_integrations/ubus.markdown
+++ b/source/_integrations/ubus.markdown
@ -20,17 +20,33 @@ opkg update
 opkg install rpcd-mod-file uhttpd-mod-ubus
 ```

-And create on your OpenWrt device a read-only user to be used by setting up the ACL file `/usr/share/rpcd/acl.d/user.json`.
+Add a new system user `hass` (or do it in any other way that you prefer):
+
+- Add line to /etc/passwd: hass:x:10001:10001:hass:/var:/bin/false
+- Add line to /etc/shadow: hass:x:0:0:99999:7:::
+
+Edit the `/etc/config/rpcd` and add the following lines:
+
+```yaml
+config login
+        option username 'hass'
+        option password '$p$hass'
+        list read hass
+        list read unauthenticated
+        list write hass
+```
+
+Then, create an ACL file at `/usr/share/rpcd/acl.d/hass.json` for the user `hass`:

 ```json
 {
-  "user": {
-    "description": "Read only user access role",
+  "hass": {
+    "description": "Access role for OpenWrt ubus integration",
    "read": {
      "ubus": {
-        "*": [ "*" ]
+        "hostapd.*": ["get_clients"],
+        "uci": ["get"]
      },
-      "uci": [ "*" ]
    },
    "write": {}
  }
--- a/source/_integrations/unifiprotect.markdown
+++ b/source/_integrations/unifiprotect.markdown
@ -59,39 +59,11 @@ UCKP with Firmware v1.x **do NOT run UniFi OS**, you must upgrade to firmware `[

 The absolute **minimal** software version is `[v1.20.0](https://community.ui.com/releases/UniFi-Protect-Application-1-20-0/d43c0905-3fb4-456b-a7ca-73aa830cb011)` for UniFi Protect. If you have an older version, you will get errors trying to set up the integration. However, the general advice is the latest 2 minor versions of UniFi Protect and hardware supported by those are supported.

-#### About UniFi Early Access
-
 <div class='note warning'>

-**Early Access releases are not supported by Home Assistant.**
+**Early Access and Release Candidate versions are not supported by Home Assistant.**

-Using Early Access versions will likely cause your UniFi Protect {% term integration %} to break unexpectedly.
-
-</div>
-
-#### Downgrading UniFi Protect
-
-In the event you accidentally upgrade to an Early Access version of UniFi Protect, you can downgrade to a stable version by either [restoring a backup](https://help.ui.com/hc/articles/360008976393) or by manually downgrading your UniFi Protect.
-
-##### Manually downgrade
-
-Manually downgrading comes with its own risks and it is not recommended unless you do not have a backup available. Some Protect versions cannot be downgraded from (like `v2.0` to `v1.21`). To downgrade, you can access your [UniFi OS Console via SSH](https://help.ui.com/hc/articles/204909374) and then do the following:
-
-```bash
-# Run this command first _only_ if you are on a 1.x firmware of the UDM Pro.
-# It is not needed for the UDM SE, UNVR, etc.
-unifi-os shell
-
-# Downgrade UniFi Protect.
-apt-get update
-apt-get install --reinstall --allow-downgrades unifi-protect=2.0.0~beta.5 -y
-```
-
-You can replace `2.0.0~beta.5` with whatever version of UniFi Protect you want to downgrade to. Any dashes in the version (`-`), replace with tilde (`~`).
-
-<div class='note'>
-
-If you want to downgrade to another Early Access version, you must have [Remote Access enabled](https://help.ui.com/hc/articles/115012240067) and have the Early Access release channel enabled.
+Using Early Access Release Candidate versions of UniFi Protect or UniFi OS will likely cause your UniFi Protect {% term integration %} to break unexpectedly. If you choose to opt into either the Early Access or the Release Candidate release channel and anything breaks in Home Assistant, you will need to wait until that version goes to the official Stable Release channel before it is expected to work.

 </div>

--- a/source/_integrations/v2c.markdown
+++ b/source/_integrations/v2c.markdown
@ -1,5 +1,5 @@
 ---
-title: V2C 
+title: V2C
 description: Instructions on how to integrate V2C Trydan EVSE with Home Assistant.
 ha_category:
  - Car
@ -10,14 +10,14 @@ ha_codeowners:
  - '@dgomes'
 ha_domain: v2c
 ha_platforms:
-  - number
  - binary_sensor
+  - number
  - sensor
  - switch
 ha_integration_type: integration
 ---

-The V2C integration allows monitoring and control of a local [V2C](https://v2c.com) Trydan EVSE in Home Assistant.
+The V2C integration allows monitoring and control of a local [V2C](https://v2charge.com/trydan/) Trydan EVSE in Home Assistant.

 There is currently support for the following platforms within Home Assistant:

--- a/source/_integrations/verisure.markdown
+++ b/source/_integrations/verisure.markdown
@ -12,8 +12,6 @@ ha_category:
 ha_release: pre 0.7
 ha_iot_class: Cloud Polling
 ha_domain: verisure
-ha_codeowners:
-  - '@frenck'
 ha_platforms:
  - alarm_control_panel
  - binary_sensor
--- a/source/_integrations/vicare.markdown
+++ b/source/_integrations/vicare.markdown
@ -17,6 +17,8 @@ ha_platforms:
  - water_heater
 ha_dhcp: true
 ha_integration_type: integration
+ha_codeowners:
+  - '@CFenner'
 ---

 The **Viessmann ViCare** {% term integration %} lets you control [Viessmann](https://www.viessmann.com) devices via the Viessmann ViCare (REST) API.
--- a/source/_integrations/weather.template.markdown
+++ b/source/_integrations/weather.template.markdown
@ -116,6 +116,10 @@ visibility_unit:
  description: Unit for visibility_template output. Valid options are km, mi, ft, m, cm, mm, in, yd.
  required: false
  type: string
+forecast_template:
+  description: Forecast data.
+  required: false
+  type: template
 forecast_daily_template:
  description: Daily forecast data.
  required: false
--- a/source/_integrations/yolink.markdown
+++ b/source/_integrations/yolink.markdown
@ -58,3 +58,4 @@ The integration is tested and verified for the following devices from YoLink:
 - YS3604 (FlexFob)
 - YS7106 (PowerFailureAlar)
 - YS4908 (Finger)
+- ‎YS7805 (Outdoor Motion Detector Sensor)
--- a/source/_integrations/zha.markdown
+++ b/source/_integrations/zha.markdown
@ -24,6 +24,7 @@ ha_codeowners:
  - '@dmulcahey'
  - '@adminiuga'
  - '@puddly'
+  - '@TheJulianJES'
 ha_domain: zha
 ha_platforms:
  - alarm_control_panel
--- a/source/_integrations/zwave_js.markdown
+++ b/source/_integrations/zwave_js.markdown
@ -132,7 +132,7 @@ The Z-Wave integration provides several special entities, some of which are avai

 ### Entities available for every Z-Wave device

-1. **Node status** sensor: This sensor shows the node status for a given Z-Wave device.  The sensor is disabled by default.  The available node statuses are explained in the [Z-Wave JS documentation](https://zwave-js.github.io/node-zwave-js/#/api/node?id=status). They can be used in state change automations. For example to ping a device when it is dead, or refresh values when it wakes up.
+1. **Node status** sensor: This sensor shows the node status for a given Z-Wave device. The sensor is disabled by default. The available node statuses are explained in the [Z-Wave JS documentation](https://zwave-js.github.io/node-zwave-js/#/api/node?id=status). They can be used in state change automations. For example to ping a device when it is dead, or refresh values when it wakes up.
 2. **Ping** button: This button can be pressed to ping a device. It is an alternative to the `zwave_js.ping` service.
 3. **Controller/node statistics** sensors: Z-Wave JS collects statistics about communications between [nodes](https://zwave-js.github.io/node-zwave-js/#/api/node?id=quotstatistics-updatedquot) and the [controller](https://zwave-js.github.io/node-zwave-js/#/api/controller?id=quotstatistics-updatedquot). The statistics can be used to troubleshoot RF issues in your environment. These statistics are available in the network configuration and device info panels. But they are also available as sensors which are disabled by default.

@ -692,7 +692,7 @@ trigger:
  # `event_source` and `event` are required
  event_source: node   # options are node, controller, and driver
  event: "interview failed"  # event names can be retrieved from the Z-Wave JS docs (see links above)
-  # `event_data` and `partial_dict_match` are optional. If `event_data` isn't included, all events of a given type for the given context will trigger the automation. When the `interview failed` event is fired, all argument live in a dictionary within the `event_data` dictionary under the `args` key. The default behavior is to require a full match of the event_data dictionary below and the dictionary that is passed to the event. By setting `partial_dict_match` to true, Home Assistant will check if the isFinal argument is true and ignore any other values in the dictionary. If this setting was false, this trigger would never fire because the dictionary always contains more keys than `isFinal` so the comparsion check would never evaluate to true.
+  # `event_data` and `partial_dict_match` are optional. If `event_data` isn't included, all events of a given type for the given context will trigger the automation. When the `interview failed` event is fired, all argument live in a dictionary within the `event_data` dictionary under the `args` key. The default behavior is to require a full match of the event_data dictionary below and the dictionary that is passed to the event. By setting `partial_dict_match` to true, Home Assistant will check if the isFinal argument is true and ignore any other values in the dictionary. If this setting was false, this trigger would never fire because the dictionary always contains more keys than `isFinal` so the comparison check would never evaluate to true.
  event_data:
    args:
      isFinal: true
@ -903,7 +903,7 @@ When trying to determine why something isn't working as you expect, or when repo

 1. Go to {% my integrations title="**Settings** > **Devices & Services**" %}.
 2. Select the **Z-Wave** integration. Then, select the three dots.
-3. From he dropdown menu, select **Download diagnostics**.
+3. From the dropdown menu, select **Download diagnostics**.

 ### How do I address interference issues?

--- a/source/_posts/2023-12-04-nabu-casa-at-the-matter-member-meeting.markdown
+++ b/source/_posts/2023-12-04-nabu-casa-at-the-matter-member-meeting.markdown
@ -0,0 +1,37 @@
+---
+layout: post
+title: "Nabu Casa at the Matter Member Meeting"
+description: "Nabu Casa represented Home Assistant, our community, and the Open Home vision at the Matter Member Meeting in Geneva. And we’ll have a dedicated live stream about Matter in January!"
+date: 2023-12-04 00:00:02
+date_formatted: "December 4, 2023"
+author: Marcel van der Veldt
+comments: true
+categories: Matter
+og_image: /images/blog/2023-11-matter-member-meeting/matter-image.jpg
+---
+
+TL;DR: We represented Home Assistant, our community, and the Open Home vision at the Matter member meeting in Geneva. We’re hosting a live stream to talk Matter in January to update you about our progress and answer your questions. Leave your questions in the comments below!
+
+Two weeks ago me, Marcel van der Veldt, and Stefan Agner, traveled to Geneva to represent Home Assistant, our community and the Open Home Vision at the Member Meeting of the Connectivity Standards Alliance (CSA). This is an important meeting where companies from all over the world meet to talk and decide about the Matter standard and how to implement it.
+
+_(Matter is the new smart home standard that promises to make everyone’s smart home devices work with each other across platforms and ecosystems, locally and privately. It’s being developed by the CSA, which is also responsible for Zigbee)._
+
+<p class='img'>
+<img src="/images/blog/2023-11-matter-member-meeting/matter-image.jpg">
+Stefan and Marcel
+</p>
+
+We were able to attend because [Nabu Casa](https://www.nabucasa.com) is a member of the CSA. We pay for this with the revenue from your Home Assistant Cloud subscriptions (thank you!). CSA membership ensures that we have access to official technical documentation and support to build Matter into Home Assistant. It also gives us a voice inside the CSA, which we use to advocate for the interests of Home Assistant users and our Open Home vision.
+
+<!--more-->
+We love to attend these events and hear amazing stories from the people we meet. When talking with engineers working on Matter in the CSA, we noticed a lot of them run Home Assistant at their own homes and are enthusiastic supporters of the project! Talking to device manufacturers made us realize that Home Assistant is used as a test platform because our Matter server is the most flexible. This is great because it increases the likelihood that Matter devices work great in Home Assistant, as devices will have been implemented and tested on it!
+
+Our participation in the development of Matter also means we’re in touch with engineers at other companies on a regular basis. One of the most popular Matter devices on the market right now, the Eve Energy Plug, has custom support for energy metering - a function not yet supported in the current Matter standard. The only way to see your energy usage was inside Eve’s own app. We’ve worked together with Eve, so we can now read the measurements from their plugs via custom Matter clusters and show them in Home Assistant! This feature will be available in the December release of Home Assistant. If you own Eve Energy Plugs, this is our early Christmas present for you.
+
+## Home Assistant and Matter
+
+We haven’t just joined the CSA; we also have dedicated developers working on making sure that Matter is a first-class citizen within Home Assistant. In our eyes, it’s ideal for Home Assistant users because of the local nature of the protocol. It is our goal to make Home Assistant an officially certified Matter controller registered with the CSA.
+
+To talk more about our ongoing progress with Matter, we’ll host a live stream in January. It will contain a full update on the state of Matter and go in-depth about what we have planned. We’ll announce the date soon.
+
+We don’t want it to be just a stream of us talking Matter to you. We know you have many questions about Matter, things that are unclear, or that you want our help to understand. So please send us your burning questions in the comments below!
--- a/source/_posts/2023-12-06-release-202312.markdown
+++ b/source/_posts/2023-12-06-release-202312.markdown
@ -0,0 +1,587 @@
+---
+layout: post
+title: "2023.12: Welcome home!"
+description: "2023.12: A beautiful new login page, new design for the thermostat card, numeric input feature for tile cards, options for the default dashboard, history dashboard showing long-term statistics, and more!"
+date: 2023-12-06 00:00:00
+date_formatted: "December 6, 2023"
+author: Franck Nijhof
+author_twitter: frenck
+comments: true
+categories:
+  - Release-Notes
+  - Core
+og_image: /images/blog/2023-12/social.png
+---
+
+<a href='/integrations/#version/2023.12'><img src='/images/blog/2023-12/social.png' style='border: 0;box-shadow: none;'></a>
+
+Home Assistant Core 2023.12! 🎄
+
+The last release of 2023 is here, and we are going out with a bang! 🎉
+
+2023 has been the [Year of the Voice](/blog/2022/12/20/year-of-voice/), and
+please stay tuned, as we will host a [final 5th chapter live stream on our YouTube channel](https://www.youtube.com/watch?v=djEkgoS5dDQ)
+on 13 December 2023, at 12:00 PST / 21:00 CET! But that is not the
+end of the voice journey... Be sure to tune in!
+
+This release has some nice quality-of-life improvements, making it feel
+like Christmas already! The thermostat card has been redesigned to match
+the gorgeous new entity dialog introduced, a new feature for the ever-improving
+tile card, re-importing blueprints, and much more!
+
+I'm most excited about the new login page that this release brings. It is
+beautiful, modern, and literally welcomes you into your own home! 🏡
+Home is where Home Assistant is, right? 😃
+
+This is it for 2023! What a year it has been! I just got one last
+thing to say this year:
+
+**Thank you for using Home Assistant! ❤️**
+
+Happy holidays & enjoy the release!
+
+../Frenck
+
+<!--more-->
+
+- [A beautiful new login page](#a-beautiful-new-login-page)
+- [New design for the thermostat card](#new-design-for-the-thermostat-card)
+- [Numeric input feature for tile cards](#numeric-input-feature-for-tile-cards)
+- [Options for the default dashboard](#options-for-the-default-dashboard)
+- [History dashboard showing long-term statistics](#history-dashboard-showing-long-term-statistics)
+- [More to-do!](#more-to-do)
+- [Re-import blueprints](#re-import-blueprints)
+- [Other noteworthy changes](#other-noteworthy-changes)
+- [New integrations](#new-integrations)
+- [Integrations now available to set up from the UI](#integrations-now-available-to-set-up-from-the-ui)
+- [Need help? Join the community!](#need-help-join-the-community)
+- [Backward-incompatible changes](#backward-incompatible-changes)
+- [Farewell to the following](#farewell-to-the-following)
+- [All changes](#all-changes)
+
+Don't forget to [join our release party live stream on YouTube](https://www.youtube.com/watch?v=2o-Uw5ZGd0M)
+6 December 2023, at 12:00 PST / 21:00 CET!
+
+<lite-youtube videoid="2o-Uw5ZGd0M" videotitle="Home Assistant 2023.12 Release Party"></lite-youtube>
+
+## A beautiful new login page
+
+The login page of Home Assistant has been redesigned to be more modern and
+match the [recent redesign of the Home Assistant onboarding](/blog/2023/09/06/release-20239/#onboarding).
+
+When Home Assistant detects you are accessing it via your local home network,
+it means you are in your trusted home environment; you will be greeted by this
+beautiful new login page, which resembles how most platforms, like Windows,
+macOS, Netflix, and others, handle this: by showing your user profiles.
+
+<img class="no-shadow" src='/images/blog/2023-12/new-login-screen.png' alt='Screenshot of the new Home Assistant login screen that allows you to click on your profile picture to log in.'>
+
+It is also much smarter! It works seamlessly with [trusted networks](/docs/authentication/providers/#trusted-networks),
+and when home, we automatically remember your login. So, no more forgetting
+to check the "keep me logged in" checkbox. 👊
+
+Of course, when logging in from outside your home network, we can't do this
+as that would give away privacy-sensitive information about your system
+and who is in it. So, when you are outside of your home network,
+the login page will ask for your username and password, just like before.
+
+<img class="no-shadow" src='/images/blog/2023-12/new-login-external-network.png' alt='Screenshot showing the new login screen, when accessing from the external network. It will still prompt for a username & password, protecting your privacy.'>
+
+Oh! And you can now change the language straight from the login page! 🌍
+
+## New design for the thermostat card
+
+[Home Assistant 2023.9 introduced](/blog/2023/09/06/release-20239/#new-climate-humidifier-and-water-heater-entity-dialogs)
+a gorgeous new entity dialog for thermostat entities. As a result of that, many
+have been asking for a similar design for the thermostat card. Well, here it is!
+
+<img class="no-shadow" src='/images/blog/2023-12/thermostat-card.png' alt='Screenshot showing two thermostat cards that showcase their stunning new looks.'>
+
+There is nothing you have to do to use this new card. Once you upgrade to this
+release, the thermostat card will automatically use this gorgeous new design.
+
+We took it one step further and added support for features. Features are
+additional functionality that you can add to a card, previously only available
+for the tile card. This release adds support for features to the
+thermostat card as well!
+
+<img class="no-shadow" src='/images/blog/2023-12/thermostat-card-features.png' alt='Screenshot that shows the new features available when configuring a thermostat card.'>
+
+For the thermostat card, it allows you to add HVAC mode buttons and presets.
+By default, these features are hidden, giving it the cleanest look possible.
+
+Oh! The same design has been applied to the (de)humidifer card, of course,
+including its respective tile features 😎.
+
+<img class="no-shadow" src='/images/blog/2023-12/humidifier-card.png' alt='Screenshot showing the same styling has been applied to the humidifier card.'>
+
+## Numeric input feature for tile cards
+
+The [tile card](/dashboards/tile/) is very powerful, and [@JosephAbbey]
+is even extending it this release by adding a new "numeric input" feature.
+
+The numeric input feature works with all number entities and number helpers.
+It allows you to control the number entity from the tile card directly
+and provides the choice to use it as a slider or as an input with up/down
+buttons.
+
+<img class="no-shadow" src='/images/blog/2023-12/tile-card-numberic-input-feature.png' alt='Screenshot showing two tile cards, one showing the button variant, the other displaying a slider.'>
+
+[@JosephAbbey]: https://github.com/JosephAbbey
+
+## Options for the default dashboard
+
+The default dashboard now has options that will allow you to change its behavior.
+You can now configure the default dashboard to hide certain areas,
+hide entities that don't belong to an area, and the option to hide the
+energy summary card.
+
+<img class="no-shadow" src='/images/blog/2023-12/dashboard-options.png' alt='Screenshot that shows the new options available for the generated default dashboard.'>
+
+When selecting **Areas**, you can choose to hide the areas but also change
+the display order of the areas by dragging them around.
+
+A first step in making the dashboards configurable, but above all,
+it gives you more control over the default dashboard, especially when you have
+just started with using Home Assistant.
+
+When adding a new dashboard, we added a dialog similar to the ones we show
+when you create new automations or scripts. It gives you the option to start
+with an empty manual dashboard or create a new default dashboard.
+
+<img class="no-shadow" src='/images/blog/2023-12/create-new-dashboard-dialog.png' alt='Screenshot that shows the new dialog you get presented when creating a new dashboard.'>
+
+## History dashboard showing long-term statistics
+
+The history dashboard did get some love from [@karwosts] this release; he
+added a big improvement to _all_ the graphs shown there.
+
+Previously, the graphs would only show the state history, limited to a few days,
+until the data is removed. This is not always very useful, for example,
+when you want to look back further in time.
+
+[@karwosts] came up with a solution for this, and the history dashboard now
+combines the state history with the recorded long-term statistics to provide
+insights into the past.
+
+<img class="no-shadow" src='/images/blog/2023-12/long-term-history-dashboard.png' alt='Screenshot showing a history graph over a longer period of time.'>
+
+The right and darker part of the graph line is provided by the state history
+(like before), and the long-term statistics provide the left and lighter part
+of the graph line (and is thus downsampled hourly data).
+
+If you have manually modified the [days to keep before purging](/integrations/recorder#configuration-variables)
+recorder on your system, consider removing that customization. With the
+long-term statistics and new feature, you most likely don’t need it anymore,
+resulting in a smaller database and, thus, faster and smaller backups.
+
+[@karwosts]: https://github.com/karwosts
+
+## More to-do!
+
+The first iteration for support for to-do lists was added in the [last release](/blog/2023/11/01/release-202311/#there-is-a-lot-to-do),
+and there has been continued work on this feature in this release.
+
+First of all, there are two new services available. A much-requested service
+to [list all items on a to-do list](/integrations/todo/#service-todoget_items)
+and a helpful service to [remove all completed items from a to-do list](/integrations/todo/#service-todoclear_items).
+
+It is nice to see integrations adding support for the to-do list feature.
+For example, the [CalDAV] integration now supports adding to-do items to your
+CalDAV server, and with [Picnic] and [OurGroceries] you can now manage your
+shopping list. In the case of Picnic, it will even look up the product you add
+in their store to your shopping list and add the product to your shopping cart.
+
+Also, when viewing a to-do list from the Home Assistant interface,
+you can copy/paste or bookmark the URL, which will always bring you back
+to the same one—a small but very helpful improvement.
+
+[CalDAV]: /integrations/caldav
+[Picnic]: /integrations/picnic
+[OurGroceries]: /integrations/ourgroceries
+
+## Re-import blueprints
+
+This release adds the ability to re-import the blueprint from the source from
+which you originally imported it. The newly downloaded blueprint will overwrite
+the existing blueprint, providing a simple "update" feature for blueprints.
+
+If you use Blueprints, for example, the ones
+[created by our incredible community](https://community.home-assistant.io/c/blueprints/38),
+you might have noticed that when you import a blueprint, it will not update
+when the author updates it. The only option you had was to manually adjust the
+YAML of the blueprint to make it match the latest version published
+by the author. To make this last bit easier, we added this re-import ability.
+
+<img class="no-shadow" src='/images/blog/2023-12/re-import-blueprint.png' alt='Screenshot showing that the overflow menu of a blueprint now provides the option to re-import an blueprint.'>
+
+A helpful feature that will make it easier to keep your blueprints in
+sync with the latest version published by the blueprint author.
+
+## Other noteworthy changes
+
+There are many more improvements in this release; here are some of the other
+noteworthy changes this release:
+
+- We have a brand new [trigger selector] for you to use in your Blueprints
+  and scripts. Thanks, [@piitaya]!
+- That is not all for selectors, [@schelv] added support for Kelvin to the
+  [color temperature selector]. Nice!
+- If you use the [IKEA IDÅSEN] desk, you will now have a height sensor!
+  Thanks [@abmantis]!
+- The [ESPHome] integration had many performance improvements, making it faster
+  and more reliable. Thanks [@bdraco]!
+- [@Lash-L] added support for displaying maps from your [Roborock] vacuums!
+  Awesome!
+- Services with a response now support handling responses when multiple entities
+  are targeted. Nice! Thanks [@eifinger]!
+- [@iMicknl] added _local API_ support for the Somfy TaHoma to the [Overkiz]
+  integration! Also, thanks [Somfy]! It's nice to see a manufacturer adding
+  local API support!
+- The [ViCare] received tons of love from [@CFenner]; keep up the good work!
+- The media browser now has support for toggling between grid and list view.
+  Thanks [@karwosts]!
+- [@emontnemery] worked hard to improve all error messages originating from
+  manual YAML configuration. The messages should now be more detailed, readable,
+  and correctly pinpoint which file and file line the error is located at. Awesome!
+- [@karwosts] created a UI when you want to add selectors to your script field!
+  Very nicely done!
+- Errors shown by Home Assistant can now be translated! While many places
+  still need to adopt this, it is a big and user-friendly step forward!
+  Outstanding job [@jbouwh]!
+
+[@abmantis]: https://github.com/abmantis
+[@bdraco]: https://github.com/bdraco
+[@CFenner]: https://github.com/CFenner
+[@eifinger]: https://github.com/eifinger
+[@emontnemery]: https://github.com/emontnemery
+[@iMicknl]: https://github.com/iMicknl
+[@jbouwh]: https://github.com/jbouwh
+[@Lash-L]: https://github.com/Lash-L
+[@piitaya]: https://github.com/piitaya
+[@schelv]: https://github.com/schelv 
+[color temperature selector]: /docs/blueprint/selectors/#color-temperature-selector
+[ESPHome]: /integrations/esphome
+[IKEA IDÅSEN]: /integrations/idasen_desk
+[Overkiz]: /integrations/overkiz
+[Roborock]: /integrations/roborock
+[Somfy]: https://www.somfy.com/
+[trigger selector]: /docs/blueprint/selectors/#trigger-selector
+[ViCare]: /integrations/vicare
+
+## New integrations
+
+We welcome the following new integrations in this release:
+
+- **[Devialet]**, added by [@fwestenberg]<br />
+  Control your wireless Devialet speakers.
+- **[Linear Garage Door]**, added by [@IceBotYT]<br />
+  Lets you control and automate your Linear garage doors.
+- **[MyPermobil]**, added by [@IsakNyberg]<br />
+  Provides various sensors for your Permobil wheelchair.
+- **[OurGroceries]**, added by [@OnFreund]<br />
+  Integrate with the OurGroceries shopping lists.
+- **[V2C]**, added by [@dgomes]<br />
+  Monitoring and control of a local V2C Trydan EVSE.
+
+[@dgomes]: https://github.com/dgomes
+[@fwestenberg]: https://github.com/fwestenberg
+[@IceBotYT]: https://github.com/IceBotYT
+[@IsakNyberg]: https://github.com/IsakNyberg
+[@OnFreund]: https://github.com/OnFreund
+[Devialet]: /integrations/devialet
+[V2C]: /integrations/v2c
+[Linear Garage Door]: /integrations/linear_garage_door
+[MyPermobil]: /integrations/mypermobil
+[OurGroceries]: /integrations/ourgroceries
+
+## Integrations now available to set up from the UI
+
+The following integrations are now available via the Home Assistant UI:
+
+- **[CalDAV]**, done by [@allenporter]
+- **[Fast.com]**, done by [@erwindouna]
+- **[Ping]**, done by [@jpbede]
+
+[@allenporter]: https://github.com/allenporter
+[@erwindouna]: https://github.com/erwindouna
+[@jpbede]: https://github.com/jpbede
+[CalDAV]: /integrations/caldav
+[Fast.com]: /integrations/fastdotcom
+[Ping]: /integrations/ping
+
+## Need help? Join the community!
+
+Home Assistant has a great community of users who are all more than willing
+to help each other out. So, join us!
+
+Our very active [Discord chat server](/join-chat) is an excellent place to be
+at, and don't forget to join our amazing [forums](https://community.home-assistant.io/).
+
+Found a bug or issue? Please report it in our [issue tracker](https://github.com/home-assistant/core/issues),
+to get it fixed! Or, check [our help page](/help) for guidance for more
+places you can go.
+
+Are you more into email? [Sign-up for our Building the Open Home Newsletter](/newsletter)
+to get the latest news about features, things happening in our community and
+other news about building an Open Home; straight into your inbox.
+
+## Backward-incompatible changes
+
+{% details "Calendar" %}
+
+`calendar.list_events` uses an outdated response data format and is now
+deprecated, pending removal in Home Assistant 2024.6.
+
+Please use `calendar.get_events`, which supports multiple entities, instead.
+
+The output of this newer service changed slightly, as it now returns a mapping
+of entity IDs to lists of events instead of a list of events.
+
+([@eifinger] - [#102481]) ([documentation](/integrations/calendar))
+
+[@eifinger]: https://github.com/eifinger
+[#102481]: https://github.com/home-assistant/core/pull/102481
+
+{% enddetails %}
+
+{% details "Counter" %}
+
+The previously deprecated `counter.configure` service has been removed.
+
+([@gjohansson-ST] - [#103204]) ([documentation](/integrations/counter))
+
+[@gjohansson-ST]: https://github.com/gjohansson-ST
+[#103204]: https://github.com/home-assistant/core/pull/103204
+
+{% enddetails %}
+
+{% details "DSMR" %}
+
+DSMR entities will not automatically update on each received DSMR telegram
+when the value between telegrams has not changed.
+
+If you rely on this, for example, for graphing, please refer to the
+[statistics integration](/integrations/statistics/).
+
+([@gigatexel] - [#104037]) ([documentation](/integrations/dsmr))
+
+[@gigatexel]: https://github.com/gigatexel
+[#104037]: https://github.com/home-assistant/core/pull/104037
+
+---
+
+For users using the 5B version: The previous gas sensor (Gas consumption)
+will change to Gas consumption mbusX. Also, multiple gas sensors will
+be possible.
+
+([@dupondje] - [#84097]) ([documentation](/integrations/dsmr))
+
+[@dupondje]: https://github.com/dupondje
+[#84097]: https://github.com/home-assistant/core/pull/84097
+
+{% enddetails %}
+
+{% details "EZVIZ" %}
+
+The previously deprecated detection sensitivity service has been removed.
+
+([@gjohansson-ST] - [#103392]) ([documentation](/integrations/ezviz))
+
+[@gjohansson-ST]: https://github.com/gjohansson-ST
+[#103392]: https://github.com/home-assistant/core/pull/103392
+
+{% enddetails %}
+
+{% details "Genius Hub" %}
+
+The initial state of the smart plug did not reflect the same state as in the
+Genius Hub application. Correcting this creates a backward-incompatible change
+in that the behavior is now correct but different.
+
+If you have an automation that relies on this state, you should check if your
+automation or script is still behaving as expected.
+
+([@GeoffAtHome] - [#102110]) ([documentation](/integrations/geniushub))
+
+[@GeoffAtHome]: https://github.com/GeoffAtHome
+[#102110]: https://github.com/home-assistant/core/pull/102110
+
+{% enddetails %}
+
+{% details "Home Assistant API" %}
+
+When calling a service via the Home Assistant REST API, the service used to be
+canceled on connection drop, which is no longer the case. If you relied on that
+behavior, you would need to revisit the logic. With this change, a connection
+drop will not cancel the service call.
+
+Also, a REST post to call a service with the `/api/services/<domain>/<service>`
+endpoint will no longer timeout after 10 seconds.
+
+([@Shulyaka] - [#102657]) ([@MartinHjelmare] - [#104709]) ([documentation](/integrations/api))
+
+[@MartinHjelmare]: https://github.com/MartinHjelmare
+[@Shulyaka]: https://github.com/Shulyaka
+[#102657]: https://github.com/home-assistant/core/pull/102657
+[#104709]: https://github.com/home-assistant/core/pull/104709
+
+{% enddetails %}
+
+{% details "HomeWizard Energy" %}
+
+The HomeWizard HWE-SKE (the wall plugs), SDM230, and SDM630 provided duplicate
+sensors for energy import and export: A total and a tariff of 1.
+
+As only a single tariff is available on those, the total and tariff 1 are
+always the same. To clean this up, tariff 1 has been removed.
+
+If you used this sensor in your energy dashboard, you will need to configure
+your energy dashboard to use the total import/export sensor instead.
+
+([@frenck] - [#104493]) ([documentation](/integrations/homewizard))
+
+[@frenck]: https://github.com/frenck
+[#104493]: https://github.com/home-assistant/core/pull/104493
+
+{% enddetails %}
+
+{% details "Nibe Heat Pump" %}
+
+S-Series entities priority-3102, hot-water-demand-mode-40057, and oper-mode-40238
+are changed from a number entity to a select entity with mapping values for the
+possible choices.
+
+If you have the old number entities enabled, you can delete them since they
+will no longer be provided by the integration.
+
+([@elupus] - [#103788]) ([documentation](/integrations/nibe_heatpump))
+
+[@elupus]: https://github.com/elupus
+[#103788]: https://github.com/home-assistant/core/pull/103788
+
+{% enddetails %}
+
+{% details "Open Exchange Rates" %}
+
+Remove rounding of the exchange rate.
+
+Exchange rates are generally more sensitive to small changes, and some quotes
+need many decimal numbers to be accurate. The Open Exchange Rates service will
+provide different significant digits for different quotes.
+
+You can change the display precision or use a template sensor to customize
+the rounding of the value.
+
+([@MartinHjelmare] - [#103972]) ([documentation](/integrations/openexchangerates))
+
+[@MartinHjelmare]: https://github.com/MartinHjelmare
+[#103972]: https://github.com/home-assistant/core/pull/103972
+
+{% enddetails %}
+
+{% details "Ping" %}
+
+The option to set a custom polling interval has been removed. If you are using
+custom interval and really need it, you can use the `homeassistant.update_entity`
+in an automation to poll at your custom pace. See our documentation on
+[defining a custom polling interval](/common-tasks/general/#defining-a-custom-polling-interval)
+for more information.
+
+([@jpbede] - [#103743]) ([documentation](/integrations/ping))
+
+[@jpbede]: https://github.com/jpbede
+[#103743]: https://github.com/home-assistant/core/pull/103743
+
+{% enddetails %}
+
+{% details "Scenes" %}
+
+Support for the, in November 2019 deprecated, attributes `brightness_pct`,
+`color_name`, `flash`, `kelvin`, `profile`, and `transition` have
+been removed from light scenes.
+
+If you have used these attributes in your scenes, you will need to adjust
+those to this change.
+
+([@emontnemery] - [#104254]) ([documentation](/integrations/scene))
+
+[@emontnemery]: https://github.com/emontnemery
+[#104254]: https://github.com/home-assistant/core/pull/104254
+
+{% enddetails %}
+
+{% details "SMTP" %}
+
+The SMTP integration will send images as attachments to a plain text email
+instead of HTML in-line when the `html` field is not set.
+
+Previous behavior was to send all images as HTML in-line even when the `html`
+field was not set. To continue sending images as in-line, please set the
+optional `html` field and include the images
+as `<img src="cid:image_name.ext">` within the HTML block as described in the
+[documentation](/integrations/smtp/#usage).
+
+([@aptalca] - [#93562]) ([documentation](/integrations/smtp))
+
+[@aptalca]: https://github.com/aptalca
+[#93562]: https://github.com/home-assistant/core/pull/93562
+
+{% enddetails %}
+
+{% details "Trafikverket Weather Station" %}
+
+Trafikverket Weather has changed its endpoint and is no longer providing the
+information for wind direction and precipitation in plain text, so
+therefore, these sensors have been removed:
+
+- Wind direction text
+- Precipitation name
+
+([@gjohansson-ST] - [#104165]) ([documentation](/integrations/trafikverket_weatherstation))
+
+[@gjohansson-ST]: https://github.com/gjohansson-ST
+[#104165]: https://github.com/home-assistant/core/pull/104165
+
+{% enddetails %}
+
+{% details "Weather" %}
+
+`weather.get_forecast` uses an outdated response data format and is now
+deprecated, pending removal in Home Assistant 2024.6.
+
+Please use `weather.get_forecasts`, which supports multiple entities instead.
+
+The output of this newer service changed slightly, as it now returns a mapping
+of entity IDs to lists of forecasts instead of a list of forecasts.
+
+([@eifinger] - [#102534]) ([documentation](/integrations/weather))
+
+[@eifinger]: https://github.com/eifinger
+[#102534]: https://github.com/home-assistant/core/pull/102534
+
+{% enddetails %}
+
+If you are a custom integration developer and want to learn about breaking
+changes and new features available for your integration: Be sure to follow our
+[developer blog][devblog]. The following are the most notable for this release:
+
+- [Config processing and error handling](https://developers.home-assistant.io/blog/2023/11/27/config-validation-and-error-handling/)
+- [Exception handling during service calls and translation support](https://developers.home-assistant.io/blog/2023/11/30/service-exceptions-and-translations/)
+- [New scaling utils and import changes](https://developers.home-assistant.io/blog/2023/12/05/scaling-utils/)
+- [Public Addon Config](https://developers.home-assistant.io/blog/2023/11/06/public-addon-config)
+
+[devblog]: https://developers.home-assistant.io/blog/
+
+## Farewell to the following
+
+The following integrations are also no longer available as of this release:
+
+- **MyQ** has been removed. Read all about it in our [blog post](/blog/2023/11/06/removal-of-myq-integration/).
+- **eQ-3 Bluetooth Smart Thermostats** have been removed. The integration has
+  been in a non-functional state for a long time.
+
+## All changes
+
+Of course, there is a lot more in this release. You can find a list of
+all changes made here: [Full changelog for Home Assistant Core 2023.12](/changelogs/core-2023.12)
--- a/source/changelogs/core-2023.12.markdown
+++ b/source/changelogs/core-2023.12.markdown
--- a/source/images/assist/assist_create_alias.png
+++ b/source/images/assist/assist_create_alias.png
--- a/source/images/assist/expose_entity_dialog.png
+++ b/source/images/assist/expose_entity_dialog.png
--- a/source/images/assist/metno_weather_entity.png
+++ b/source/images/assist/metno_weather_entity.png
--- a/source/images/assist/weather_entity_voice_assistant.png
+++ b/source/images/assist/weather_entity_voice_assistant.png
--- a/source/images/blog/2023-11-matter-member-meeting/matter-image.jpg
+++ b/source/images/blog/2023-11-matter-member-meeting/matter-image.jpg
--- a/source/images/blog/2023-12/create-new-dashboard-dialog.png
+++ b/source/images/blog/2023-12/create-new-dashboard-dialog.png
--- a/Show More
+++ b/Show More