Merge branch 'current' into next

CODEOWNERS

@@ -188,10 +188,11 @@ source/_integrations/dnsip.markdown @gjohansson-ST
 source/_integrations/doorbird.markdown @oblogic7 @bdraco @flacjacket
 source/_integrations/dooya.markdown @starkillerOG
 source/_integrations/dormakaba_dkey.markdown @emontnemery
+source/_integrations/downloader.markdown @erwindouna
 source/_integrations/dremel_3d_printer.markdown @tkdrob
 source/_integrations/drop_connect.markdown @ChandlerSystems @pfrazer
 source/_integrations/dsmr.markdown @Robbie1221 @frenck
-source/_integrations/dsmr_reader.markdown @depl0y @glodenox
+source/_integrations/dsmr_reader.markdown @sorted-bits @glodenox
 source/_integrations/duotecno.markdown @cereal2nd
 source/_integrations/duquesne_light.markdown @tronikos
 source/_integrations/dwd_weather_warnings.markdown @runningman84 @stephan192 @andarotajo
@@ -273,6 +274,7 @@ source/_integrations/frontend.markdown @home-assistant/frontend
 source/_integrations/frontier_silicon.markdown @wlcrs
 source/_integrations/fujitsu_anywair.markdown @Bre77
 source/_integrations/fully_kiosk.markdown @cgarwood
+source/_integrations/fyta.markdown @dontinelli
 source/_integrations/garages_amsterdam.markdown @klaasnicolaas
 source/_integrations/gardena_bluetooth.markdown @elupus
 source/_integrations/gaviota.markdown @starkillerOG
@@ -338,7 +340,7 @@ source/_integrations/homeassistant_sky_connect.markdown @home-assistant/core
 source/_integrations/homeassistant_yellow.markdown @home-assistant/core
 source/_integrations/homekit.markdown @bdraco
 source/_integrations/homekit_controller.markdown @Jc2k @bdraco
-source/_integrations/homematic.markdown @pvizeli @danielperna84
+source/_integrations/homematic.markdown @pvizeli
 source/_integrations/homewizard.markdown @DCSBL
 source/_integrations/honeywell.markdown @rdfurman @mkmer
 source/_integrations/http.markdown @home-assistant/core
@@ -502,7 +504,7 @@ source/_integrations/mystrom.markdown @fabaff
 source/_integrations/myuplink.markdown @pajzo @astrandb
 source/_integrations/nam.markdown @bieniu
 source/_integrations/nanoleaf.markdown @milanmeu
-source/_integrations/neato.markdown @dshokouhi @Santobert
+source/_integrations/neato.markdown @Santobert
 source/_integrations/nederlandse_spoorwegen.markdown @YarmoM
 source/_integrations/ness_alarm.markdown @nickw444
 source/_integrations/nest.markdown @allenporter
@@ -541,6 +543,7 @@ source/_integrations/nzbget.markdown @chriscla
 source/_integrations/obihai.markdown @dshokouhi @ejpenney
 source/_integrations/octoprint.markdown @rfleming71
 source/_integrations/ohmconnect.markdown @robbiet480
+source/_integrations/ollama.markdown @synesthesiam
 source/_integrations/ombi.markdown @larssont
 source/_integrations/omnilogic.markdown @oliver84 @djtimca @gentoosu
 source/_integrations/onboarding.markdown @home-assistant/core
@@ -638,7 +641,6 @@ source/_integrations/recollect_waste.markdown @bachya
 source/_integrations/recorder.markdown @home-assistant/core
 source/_integrations/recovery_mode.markdown @home-assistant/core
 source/_integrations/refoss.markdown @ashionky
-source/_integrations/rejseplanen.markdown @DarkFox
 source/_integrations/remote.markdown @home-assistant/core
 source/_integrations/renault.markdown @epenet
 source/_integrations/renson.markdown @jimmyd-be
@@ -694,6 +696,7 @@ source/_integrations/sentry.markdown @dcramer @frenck
 source/_integrations/senz.markdown @milanmeu
 source/_integrations/serial.markdown @fabaff
 source/_integrations/seven_segments.markdown @fabaff
+source/_integrations/seventeentrack.markdown @shaiu
 source/_integrations/sfr_box.markdown @epenet
 source/_integrations/sharkiq.markdown @JeffResc @funkybunch
 source/_integrations/shell_command.markdown @home-assistant/core
@@ -726,6 +729,7 @@ source/_integrations/smarttub.markdown @mdz
 source/_integrations/smarty.markdown @z0mbieprocess
 source/_integrations/smhi.markdown @gjohansson-ST
 source/_integrations/sms.markdown @ocalvo
+source/_integrations/smud.markdown @tronikos
 source/_integrations/snapcast.markdown @luar123
 source/_integrations/snooz.markdown @AustinBrunkhorst
 source/_integrations/solaredge.markdown @frenck

Gemfile

@@ -3,7 +3,7 @@ source 'https://rubygems.org'
 ruby '> 2.5.0'
 
 group :development do
-  gem 'rake', '13.1.0'
+  gem 'rake', '13.2.1'
   gem 'jekyll', '4.3.3'
   gem 'compass', '1.0.3'
   gem 'sass-globbing', '1.1.5'
@@ -11,7 +11,7 @@ group :development do
   # > 2.1.0 causes slowdowns https://github.com/sass/sassc-ruby/issues/189
   gem 'sassc', '2.1.0'
   gem 'rubocop', '1.62.1'
-  gem 'ruby-lsp', '0.14.6'
+  gem 'ruby-lsp', '0.16.1'
   gem 'rackup', '2.1.0'
 end
 

Gemfile.lock

@@ -27,7 +27,7 @@ GEM
     eventmachine (1.2.7)
     ffi (1.16.3)
     forwardable-extended (2.6.0)
-    google-protobuf (4.26.0-x86_64-linux)
+    google-protobuf (4.26.1-x86_64-linux)
       rake (>= 13)
     http_parser.rb (0.8.0)
     i18n (1.14.4)
@@ -60,7 +60,7 @@ GEM
       nokogiri (~> 1.12)
     jekyll-watch (2.2.1)
       listen (~> 3.0)
-    json (2.7.1)
+    json (2.7.2)
     kramdown (2.4.0)
       rexml
     kramdown-parser-gfm (1.1.0)
@@ -83,7 +83,7 @@ GEM
     pathutil (0.16.2)
       forwardable-extended (~> 2.6)
     prism (0.24.0)
-    public_suffix (5.0.4)
+    public_suffix (5.0.5)
     racc (1.7.3)
     rack (3.0.10)
     rack-protection (4.0.0)
@@ -95,7 +95,7 @@ GEM
       rack (>= 3)
       webrick (~> 1.8)
     rainbow (3.1.1)
-    rake (13.1.0)
+    rake (13.2.1)
     rb-fsevent (0.11.2)
     rb-inotify (0.10.1)
       ffi (~> 1.0)
@@ -115,7 +115,7 @@ GEM
       unicode-display_width (>= 2.4.0, < 3.0)
     rubocop-ast (1.31.2)
       parser (>= 3.3.0.4)
-    ruby-lsp (0.14.6)
+    ruby-lsp (0.16.1)
       language_server-protocol (~> 3.17.0)
       prism (>= 0.22.0, < 0.25)
       sorbet-runtime (>= 0.5.10782)
@@ -123,7 +123,7 @@ GEM
     ruby2_keywords (0.0.5)
     safe_yaml (1.0.5)
     sass (3.4.25)
-    sass-embedded (1.72.0-x86_64-linux-gnu)
+    sass-embedded (1.74.1-x86_64-linux-gnu)
       google-protobuf (>= 3.25, < 5.0)
     sass-globbing (1.1.5)
       sass (>= 3.1)
@@ -135,7 +135,7 @@ GEM
       rack-protection (= 4.0.0)
       rack-session (>= 2.0.0, < 3)
       tilt (~> 2.0)
-    sorbet-runtime (0.5.11311)
+    sorbet-runtime (0.5.11332)
     stringex (2.8.6)
     terminal-table (3.0.2)
       unicode-display_width (>= 1.1.1, < 3)
@@ -159,9 +159,9 @@ DEPENDENCIES
   jekyll-toc (= 0.18.0)
   nokogiri (= 1.16.3)
   rackup (= 2.1.0)
-  rake (= 13.1.0)
+  rake (= 13.2.1)
   rubocop (= 1.62.1)
-  ruby-lsp (= 0.14.6)
+  ruby-lsp (= 0.16.1)
   sass-globbing (= 1.1.5)
   sassc (= 2.1.0)
   sinatra (= 4.0.0)

_config.yml

@@ -109,9 +109,9 @@ social:
 
 # Home Assistant release details
 current_major_version: 2024
-current_minor_version: 3
-current_patch_version: 3
-date_released: 2024-03-22
+current_minor_version: 4
+current_patch_version: 1
+date_released: 2024-04-05
 
 # Either # or the anchor link to latest release notes in the blog post.
 # Must be prefixed with a # and have double quotes around it.
@@ -195,7 +195,7 @@ toc:
 installation:
   container: "ghcr.io/home-assistant/home-assistant"
   versions:
-    python: "3.11"
+    python: "3.12"
   types:
     odroid:
       board: ODROID

source/_docs/energy/water.markdown

@@ -44,6 +44,10 @@ If your water meter lacks a rotary disk, magnetic disk, or coil. There are alter
 
 - [AI-on-the-edge-device](https://github.com/jomjol/AI-on-the-edge-device) is a project running on an ESP32-CAM and can be fully integrated into Home Assistant using the Home Assistant Discovery Functionality of MQTT. It digitalizes your gas/water/electricity meter display and provides its data in various ways.![Photo of the AI-on-the-edge-device Workflow](/images/docs/energy/
 
+If you have a Culligan Water Softener, you may be able to interface with the inbuilt `DEBUG PORT` and receive water usage stats including `Gallons` (gal), `Gallons Per Minute` (gal/min), and `Gallons to Recharge` (gal):
+
+- [cullAssistant](https://github.com/LelandSindt/cullAssistant) (ESPHome)
+
 Alternatively, the following shops sell ESPHome-based devices that use a 3-phase light sensor to detect a rotating disk in your water meter and convert this to the amount of water used in milliliters (ml):
 - [Muino water meter reader](https://watermeter.muino.nl/) (ESPHome)
 

source/_docs/organizing/areas.markdown

@@ -20,7 +20,7 @@ Follow these steps to create a new area from the **Areas** view.
      - This number can later be used for sorting.
    - Add an image representing that area.
    - Add an **Alias**.
-     - Aliases are alternative names used in [voice assistants](/voice_control/aliases/) to refer to this floor.
+     - Aliases are alternative names used in [voice assistants](/voice_control/aliases/) to refer to an area, entity, or floor.
 
     ![Create area dialog](/images/organizing/create_area_01.png)
 3. Select **Add**.

source/_docs/organizing/categories.markdown

@@ -30,7 +30,8 @@ Follow these steps to create a new category.
    - From the list, select all the items to which you want to apply a category.
    - In the top right corner, select **Move to category**.
    - Then, select the category from the list.
-4. Once categories are applied, table items can be grouped by category.
+4. Once categories are applied, the table items are grouped by those categories.
+   - The example shows 2 categories: Coffee and housekeeping. 
 
     ![Group table items by category](/images/organizing/category_02.png)
 

source/_docs/organizing/floors.markdown

@@ -18,7 +18,7 @@ Follow these steps to create a new floor.
      - This number can later be used for sorting.
    - Add an icon (We use [Material icons](https://pictogrammers.com/library/mdi/)).
    - Add an **Alias**.
-     - Aliases are alternative names used in [voice assistants](/voice_control/aliases/) to refer to this floor.
+     - Aliases are alternative names used in [voice assistants](/voice_control/aliases/) to refer to an entity, area, or floor.
 
     ![Create floor dialog](/images/organizing/create_floor_01.png)
 3. Select **Add**.

source/_docs/scripts/service-calls.markdown

@@ -80,7 +80,7 @@ entity_id: switch.ac
 ### Using the Services Developer Tool
 
 You can use the Services Developer Tool to test data to pass in a service call.
-For example, you may test turning on or off a 'group' (See [groups] for more info)
+For example, you may test turning on or off a 'group' (See [groups](/integrations/group/) for more info)
 
 To turn a group on or off, pass the following info:
 

source/_includes/asides/docs_navigation.html

@@ -23,6 +23,13 @@
           </li>
         </ul>
       </li>
+      <li>
+        <b>{% active_link /docs/frontend/ Frontend %}</b>
+        <ul>
+          <li>{% active_link /docs/organizing/ Organizing %}</li>
+          <li>{% active_link /docs/frontend/icons/ Icons%}</li>
+        </ul>
+      </li>
       <li>
         <b>{% active_link /docs/configuration/ Configuration.yaml %}</b>
         <ul>
@@ -121,17 +128,6 @@
           <li>{% active_link /docs/blueprint/selectors/ Selectors %}</li>
         </ul>
       </li>
-      <li>
-        <b>{% active_link /docs/frontend/ Frontend %}</b>
-        <ul>
-          <li>{% active_link /dashboards Dashboards %}</li>
-          <li>{% active_link /docs/organizing/ Organizing %}</li>
-          <li>{% active_link /docs/frontend/icons/ Icons%}</li>
-          <li>
-            {% active_link /docs/frontend/browsers/ Browser compatibility list%}
-          </li>
-        </ul>
-      </li>
       <li>
         <b>{% active_link /docs/backend/ Backend %}</b>
         <ul>

source/_integrations/apcupsd.markdown

@@ -13,6 +13,7 @@ ha_codeowners:
   - '@yuxincs'
 ha_platforms:
   - binary_sensor
+  - diagnostics
   - sensor
 ha_integration_type: integration
 ha_quality_scale: silver

source/_integrations/bring.markdown

@@ -26,4 +26,4 @@ For authentication, the integration requires the `email` and `password` you used
 - [Bring!](https://www.getbring.com/)
 - [To-do list integration documentation](/integrations/todo)
 - [List of to-do list integrations](/integrations/#to-do-list)
-- [To-do list card](/dashboards/todo-list/)
+- [To-do list card](/dashboards/todo-list/)

source/_integrations/caldav.markdown

@@ -212,4 +212,4 @@ password.
 
 - [To-do list integration documentation](/integrations/todo)
 - [List of to-do list integrations](/integrations/#to-do-list)
-- [To-do list card](/dashboards/todo-list/)
+- [To-do list card](/dashboards/todo-list/)

source/_integrations/comelit.markdown

@@ -18,7 +18,6 @@ ha_iot_class: Local Polling
 ha_platforms:
   - alarm_control_panel
   - climate
-  - humidifier
   - cover
   - humidifier
   - light

source/_integrations/command_line.markdown

@@ -43,7 +43,7 @@ command_line:
         command:
           description: The action to take to get the value.
           required: true
-          type: string
+          type: template
         command_timeout:
           description: Defines number of seconds for command timeout.
           required: false
@@ -172,7 +172,7 @@ command_line:
         command:
           description: The action to take to get the value.
           required: true
-          type: string
+          type: template
         command_timeout:
           description: Defines number of seconds for command timeout
           required: false

source/_integrations/control4.markdown

@@ -9,7 +9,6 @@ ha_iot_class: Local Polling
 ha_config_flow: true
 ha_codeowners:
   - '@lawtancool'
-  - '@nalin29'
 ha_domain: control4
 ha_ssdp: true
 ha_platforms:

source/_integrations/downloader.markdown

@@ -9,6 +9,7 @@ ha_domain: downloader
 ha_codeowners:
   - '@erwindouna'
 ha_integration_type: integration
+ha_config_flow: true
 ---
 
 The **Downloader** {% term integration %} provides a service to download files. It will raise an error and not continue to set itself up when the download directory does not exist. The directory needs to be writable for the user that is running Home Assistant.

source/_integrations/dsmr_reader.markdown

@@ -9,7 +9,7 @@ ha_config_flow: true
 ha_mqtt: true
 ha_release: 0.103
 ha_codeowners:
-  - '@depl0y'
+  - '@sorted-bits'
   - '@glodenox'
 ha_domain: dsmr_reader
 ha_platforms:

source/_integrations/dte_energy_bridge.markdown

@@ -1,5 +1,5 @@
 ---
-title: DTE Energy Bridge (2020 and older hardware only)
+title: DTE Energy Bridge
 description: Setup early-model DTE Energy Bridge with Home Assistant.
 ha_category:
   - Energy

source/_integrations/elmax.markdown

@@ -15,6 +15,7 @@ ha_platforms:
   - cover
   - switch
 ha_integration_type: integration
+ha_zeroconf: true
 ---
 
 The Elmax integration enables Home Assistant integration with 

source/_integrations/fastdotcom.markdown

@@ -12,6 +12,7 @@ ha_codeowners:
   - '@erwindouna'
 ha_domain: fastdotcom
 ha_platforms:
+  - diagnostics
   - sensor
 ha_integration_type: integration
 ---

source/_integrations/filesize.markdown

@@ -21,6 +21,8 @@ The `filesize` sensor is for displaying the size in MB of a file.
 
 File paths must also be added to [allowlist_external_dirs](/docs/configuration/basic/) in your `configuration.yaml`.
 
+File paths should be absolute paths. For example: `/config/home-assistant_v2.db` to monitor the size of the default database.
+
 </div>
 
 {% include integrations/config_flow.md %}

source/_integrations/filter.markdown

@@ -117,7 +117,7 @@ filters:
 
 <div class="note warning">
 
-When configuring a `window_size` that is not a time and with a value larger than the default of `1`, the database must examine nearly every stored state for that entity during Home Assistant startup. If you have modified the [Recorder `purge_keep_days`](/integrations/recorder/#purge_keep_days) value or have many states stored in the database for the filtered entity, this can cause your Home Assistant instance can to respond poorly during startup.
+When configuring a `window_size` that is not a time and with a value larger than the default of `1`, the database must examine nearly every stored state for that entity during Home Assistant startup. If you have modified the [Recorder `purge_keep_days`](/integrations/recorder/#purge_keep_days) value or have many states stored in the database for the filtered entity, this can cause your Home Assistant instance to respond poorly during startup.
 
 </div>
 

source/_integrations/freebox.markdown

@@ -45,6 +45,12 @@ You can find out your Freebox host and port by opening this address <http://mafr
 The returned JSON should contain an `api_domain` (`host`) and a `https_port` (`port`).
 Please consult the [API documentation](https://dev.freebox.fr/sdk/os/) for more information.
 
+<div class='note warning'>
+
+The `host` (ex: xxxxxxxx.fbxos.fr) and `port` given by <http://mafreebox.freebox.fr/api_version> refers to your Freebox public IP address and may not work if your Home Assistant server is located inside your local LAN. For local API access, you can alternatively use `host` = *mafreebox.freebox.fr* and `port` = *443*.
+
+</div>
+
 ### Initial setup
 
 <div class='note warning'>

source/_integrations/fyta.markdown

@@ -11,7 +11,7 @@ ha_codeowners:
 ha_domain: fyta
 ha_platforms:
   - sensor
-ha_integration_type: integration
+ha_integration_type: hub
 ---
 
 The **FYTA** {% term integration %} uses the open API of [FYTA](https://www.fyta.de) to obtain the data from your plant sensors and integrate these into Home Assistant.
@@ -39,4 +39,3 @@ The following sensors are currently available per plant:
 | moisture              | %      | Moisture measured by sensor                |
 | salinity              | mS/cm  | Salinity measured by sensor (measured as conductivity)|
 | battery_level         | %      | Battery level of the sensor                |
-

source/_integrations/google_tasks.markdown

@@ -88,4 +88,4 @@ If you have an error with your credentials, you can delete them in the [Applicat
 
 - [To-do list integration documentation](/integrations/todo)
 - [List of to-do list integrations](/integrations/#to-do-list)
-- [To-do list card](/dashboards/todo-list/)
+- [To-do list card](/dashboards/todo-list/)

source/_integrations/homematic.markdown

@@ -15,7 +15,6 @@ ha_iot_class: Local Push
 ha_release: 0.23
 ha_codeowners:
   - '@pvizeli'
-  - '@danielperna84'
 ha_domain: homematic
 ha_platforms:
   - binary_sensor

source/_integrations/homeworks.markdown

@@ -2,9 +2,9 @@
 title: Lutron Homeworks
 description: How to use Lutron Homeworks Series 4 & 8 with Home Assistant.
 ha_category:
-  - Hub
   - Binary sensor
   - Button
+  - Hub
   - Light
 ha_release: 0.85
 ha_iot_class: Local Push
@@ -14,6 +14,7 @@ ha_platforms:
   - button
   - light
 ha_integration_type: integration
+ha_config_flow: true
 ---
 
 [Lutron](https://www.lutron.com/) is an American lighting control company. The Lutron Homeworks Series 4 & 8 systems are relatively old (~2003), and use RS-232 connections to communicate with home automation systems.  The `homeworks` integration in Home Assistant is responsible for communicating with the main controller for these systems.  Communication is through an ethernet to serial converter (NPort, for example).

source/_integrations/husqvarna_automower.markdown

@@ -16,6 +16,7 @@ ha_codeowners:
 ha_platforms:
   - binary_sensor
   - device_tracker
+  - diagnostics
   - lawn_mower
   - select
   - sensor

source/_integrations/hyperion.markdown

@@ -14,8 +14,8 @@ ha_ssdp: true
 ha_platforms:
   - camera
   - light
-  - switch
   - sensor
+  - switch
 ha_integration_type: integration
 ---
 

source/_integrations/ipma.markdown

@@ -10,6 +10,7 @@ ha_codeowners:
   - '@dgomes'
 ha_domain: ipma
 ha_platforms:
+  - diagnostics
   - sensor
   - weather
 ha_integration_type: integration

source/_integrations/kitchen_sink.markdown

@@ -12,6 +12,7 @@ ha_iot_class: Calculated
 ha_platforms:
   - button
   - image
+  - lawn_mower
   - lock
   - sensor
   - switch

source/_integrations/local_todo.markdown

@@ -1,5 +1,5 @@
 ---
-title: Local to-do
+title: Local To-do
 description: Instructions on how to use local to-do lists in Home Assistant.
 ha_category:
   - To-do list
@@ -26,4 +26,4 @@ about to-do list entities.
 ## Related topics
 
 - [**To-do list** integration](/integrations/todo)
-- [To-do list card](/dashboards/todo-list/)
+- [To-do list card](/dashboards/todo-list/)

source/_integrations/microbees.markdown

@@ -1,9 +1,9 @@
 ---
 title: microBees
 description: Instructions on how to integrate microBees devices into Home Assistant.
-ha_category:  
-  - Cover
+ha_category:
   - Button
+  - Cover
   - Light
   - Sensor
   - Switch
@@ -14,10 +14,9 @@ ha_config_flow: true
 ha_domain: microbees
 ha_iot_class: Cloud Polling
 ha_platforms:
-  - switch
-  - cover
   - binary_sensor
   - button
+  - cover
   - light
   - sensor
   - switch

source/_integrations/modbus.markdown

@@ -16,7 +16,7 @@ ha_platforms:
   - light
   - sensor
   - switch
-ha_quality_scale: gold
+ha_quality_scale: platinum
 ha_integration_type: integration
 ---
 

source/_integrations/motionblinds_ble.markdown

@@ -14,7 +14,7 @@ ha_platforms:
   - button
   - cover
   - select
-ha_integration_type: integration
+ha_integration_type: device
 ---
 
 This {% term integration %} adds support for [Motionblinds](https://motionblinds.com/) Bluetooth motors. Want to motorize your existing blinds? This can be done with Motionblinds motor CMD-03. Made-to-measure window coverings with Motionblinds are available through a worldwide reseller network.

source/_integrations/mqtt.markdown

@@ -25,6 +25,7 @@ ha_platforms:
   - fan
   - humidifier
   - image
+  - lawn_mower
   - light
   - lock
   - number

source/_integrations/neato.markdown

@@ -11,7 +11,6 @@ ha_iot_class: Cloud Polling
 ha_release: 0.33
 ha_config_flow: true
 ha_codeowners:
-  - '@dshokouhi'
   - '@Santobert'
 ha_domain: neato
 ha_platforms:

source/_integrations/notify.markdown

@@ -87,5 +87,3 @@ action:
 ```
 
 {% endraw %}
-
-

source/_integrations/numato.markdown

@@ -15,7 +15,7 @@ ha_platforms:
   - binary_sensor
   - sensor
   - switch
-ha_integration_type: integration
+ha_integration_type: hub
 ---
 
 The `numato` integration is the base for all related GPIO platforms of the

source/_integrations/ollama.markdown

@@ -16,7 +16,7 @@ The **Ollama** {% term integration %} adds a conversation agent in Home Assistan
 
 This conversation agent is unable to control your house. The Ollama conversation agent can be used in automations, but not as a [sentence trigger](/docs/automation/trigger/#sentence-trigger). It can only query information that has been provided by Home Assistant. To be able to answer questions about your house, Home Assistant will need to provide Ollama with the details of your house, which include areas, devices, and their states. 
 
-This integration requires an external Ollama server, which is available for macOS, Linux, and Windows. Follow the [download instructions](https://ollama.com/) to install the server.
+This integration requires an external Ollama server, which is available for macOS, Linux, and Windows. Follow the [download instructions](https://ollama.com/download) to install the server. Once installed, configure Ollama to be [accessible over the network](https://github.com/ollama/ollama/blob/main/docs/faq.md#how-can-i-expose-ollama-on-my-network).
 
 {% include integrations/config_flow.md %}
 

source/_integrations/ourgroceries.markdown

@@ -24,4 +24,4 @@ It adds a [to-do list entity](/integrations/todo) for each shopping list, allowi
 - [OurGroceries](https://www.ourgroceries.com/)
 - [To-do list integration documentation](/integrations/todo)
 - [List of to-do list integrations](/integrations/#to-do-list)
-- [To-do list card](/dashboards/todo-list/)
+- [To-do list card](/dashboards/todo-list/)

source/_integrations/permobil.markdown

@@ -10,6 +10,7 @@ ha_codeowners:
   - '@IsakNyberg'
 ha_config_flow: true
 ha_platforms:
+  - binary_sensor
   - sensor
 ha_integration_type: integration
 ---

source/_integrations/piper.markdown

@@ -19,6 +19,7 @@ ha_platforms:
   - stt
   - switch
   - tts
+  - wake_word
 ha_iot_class: Local Push
 ha_zeroconf: true
 ---

source/_integrations/profiler.markdown

@@ -198,4 +198,4 @@ Logs statistics from [lru_cache](https://docs.python.org/3/library/functools.htm
 | ---------------------- | -------- | -------------------------------------- |
 | `enabled`              | yes      | Boolean to enable asyncio debug.       |
 
-When `set_asyncio_debug` is enabled, `asyncio` will run in [debug mode](https://docs.python.org/3/library/asyncio-dev.html#debug-mode). Use this service to help identify an integration that is blocking the event loop.
+When `set_asyncio_debug` is enabled, `asyncio` will run in [debug mode](https://docs.python.org/3/library/asyncio-dev.html#debug-mode). Use this service to help identify an integration that is blocking the event loop.

source/_integrations/rejseplanen.markdown

@@ -6,8 +6,6 @@ ha_category:
 ha_iot_class: Cloud Polling
 ha_release: 0.88
 ha_domain: rejseplanen
-ha_codeowners:
-  - '@DarkFox'
 ha_platforms:
   - sensor
 ha_integration_type: integration

source/_integrations/reolink.markdown

@@ -266,6 +266,7 @@ The following models have been tested and confirmed to work:
 - [RLC-822A](https://reolink.com/product/rlc-822a/)
 - [RLC-823A](https://reolink.com/product/rlc-823a/)
 - [RLC-833A](https://reolink.com/product/rlc-833a/)
+- [RLC-1212A](https://reolink.com/product/rlc-1212a/)
 - [RLC-1224A](https://reolink.com/product/rlc-1224a/)
 - [RLN8-410 NVR](https://reolink.com/product/rln8-410/)
 - [RLN16-410 NVR](https://reolink.com/product/rln16-410/)

source/_integrations/schedule.markdown

@@ -1,6 +1,6 @@
 ---
 title: Schedule
-description: Instructions on how use make weekly schedule in Home Assistant.
+description: Instructions on how to make a weekly schedule in Home Assistant.
 ha_category:
   - Automation
   - Helper

source/_integrations/seventeentrack.markdown

@@ -11,7 +11,7 @@ ha_codeowners:
 ha_domain: seventeentrack
 ha_platforms:
   - sensor
-ha_integration_type: integration
+ha_integration_type: service
 ---
 
 The seventeentrack {% term integration %} allows users to get package data tied to their [17track.net](https://www.17track.net) account. The integration creates both summary sensors, which show the number of packages in a current state (e.g., "In Transit"), as well as individual sensors for each package within the account.

source/_integrations/shelly.markdown

@@ -5,8 +5,8 @@ ha_category:
   - Binary sensor
   - Climate
   - Cover
-  - Event
   - Energy
+  - Event
   - Light
   - Number
   - Sensor

source/_integrations/smud.markdown

@@ -4,7 +4,7 @@ description: Get energy usage from Sacramento Municipal Utility District (SMUD)
 ha_category:
   - Energy
   - Sensor
-ha_release: 2024.4
+ha_release: 2023.8
 ha_domain: smud
 ha_integration_type: virtual
 ha_supporting_domain: opower

source/_integrations/synology_srm.markdown

@@ -58,7 +58,7 @@ verify_ssl:
   type: boolean
 {% endconfiguration %}
 
-It's not possible to create another account in SRM with admin permissions. You'll need to use your admin account (or the one you renamed at creation) for this connection.
+For instructions on creating multiple administrators on SRM, please refer to the [Synology Knowledge Center](https://kb.synology.com/en-id/SRM/tutorial/Create_multiple_administrator_accounts_on_Synology_Router).
 
 List of models known to be supported:
 

source/_integrations/teslemetry.markdown

@@ -89,4 +89,3 @@ The integration will create sensor entities for a variety of metrics that relate
 - Power
 - State code (disabled by default)
 - Vehicle
-

source/_integrations/todo.markdown

@@ -144,4 +144,4 @@ target:
 ## Related topics
 
 - [Local to-do integration](/integrations/local_todo/)
-- [To-do list card](/dashboards/todo-list/)
+- [To-do list card](/dashboards/todo-list/)

source/_integrations/todoist.markdown

@@ -205,4 +205,4 @@ Here are two example JSON payloads resulting in the same task:
 - [To-do list integration documentation](/integrations/todo)
 - [List of to-do list integrations](/integrations/#to-do-list)
 - [To-do list card](/dashboards/todo-list/)- 
-- [Dashboards](/dashboards/dashboards/)
+- [Dashboards](/dashboards/dashboards/)

source/_integrations/unifi.markdown

@@ -34,6 +34,7 @@ There is currently support for the following device types within Home Assistant:
 - [Button](#button)
 - [Image](#image)
 - [Presence detection](#presence-detection)
+- [Services](#services)
 - [Switch](#switch)
 - [Sensor](#sensor)
 - [Firmware updates](#firmware-updates)

source/_integrations/webmin.markdown

@@ -11,6 +11,7 @@ ha_codeowners:
 ha_domain: webmin
 ha_integration_type: device
 ha_platforms:
+  - diagnostics
   - sensor
 ---
 

source/_integrations/whirlpool.markdown

@@ -13,6 +13,7 @@ ha_codeowners:
 ha_domain: whirlpool
 ha_platforms:
   - climate
+  - diagnostics
   - sensor
 ha_integration_type: hub
 ---

source/_integrations/whisper.markdown

@@ -19,6 +19,7 @@ ha_platforms:
   - stt
   - switch
   - tts
+  - wake_word
 ha_iot_class: Local Push
 ha_zeroconf: true
 ---

source/_integrations/yolink.markdown

@@ -27,6 +27,7 @@ ha_platforms:
   - sensor
   - siren
   - switch
+  - valve
 ha_integration_type: integration
 ---
 

source/_posts/2024-04-03-release-20244.markdown

@@ -0,0 +1,846 @@
+---
+layout: post
+title: "2024.4: Organize all the things!"
+description: "Time for spring cleaning 🧹 Introducing new ways to organize your automations (and more) with floors, labels, and categories. Easily add Matter devices from other controllers, and two brand new map and webpage dashboards."
+date: 2024-04-03 00:00:00
+date_formatted: "April 3, 2024"
+author: Franck Nijhof
+author_twitter: frenck
+comments: true
+categories:
+  - Release-Notes
+  - Core
+og_image: /images/blog/2024-04/social.png
+---
+
+<a href='/integrations/#version/2024.4'><img src='/images/blog/2024-04/social.png' style='border: 0;box-shadow: none;'></a>
+
+Home Assistant Core 2024.4! 🌱 🌻
+
+Are you ready for another massive release? This release addresses the most
+requested feature in Home Assistant history: grouping automations! 🎉
+
+But why stop there?
+
+This release brings excellent new features to our user interface that house not
+one, not two, but three! new ways to organize your Home Assistant setup!
+The best part is that it is not just for automations, but for everything! 🤯
+
+Perfect timing: spring is here! Time to spring clean your Home Assistant
+setup by adding some organization to your configuration! 🧹
+
+Enjoy the release! 🌞
+
+../Frenck
+
+<!--more-->
+
+- [Home Assistant spring cleaning! 🧹 New ways to get your automations (and more) organized](#home-assistant-spring-cleaning--new-ways-to-get-your-automations-and-more-organized)
+- [Upgraded tables!](#upgraded-tables)
+  - [A new toolbar](#a-new-toolbar)
+  - [Filter panel](#filter-panel)
+  - [Item grouping](#item-grouping)
+  - [Selection mode and batch actions](#selection-mode-and-batch-actions)
+- [Three new ways to organize](#three-new-ways-to-organize)
+  - [Floors: Help Home Assistant understand your house](#floors-help-home-assistant-understand-your-house)
+  - [Labels: Tag everything any way you want](#labels-tag-everything-any-way-you-want)
+  - [Categories: Make each settings page easier to browse](#categories-make-each-settings-page-easier-to-browse)
+  - [Time to clean up your Home Assistant!](#time-to-clean-up-your-home-assistant)
+- [Map dashboard](#map-dashboard)
+- [Webpage dashboard](#webpage-dashboard)
+- [Define the columns in the section view](#define-the-columns-in-the-section-view)
+- [Adding Matter devices from other controllers](#adding-matter-devices-from-other-controllers)
+- [Lock behavior improvements](#lock-behavior-improvements)
+- [Even more performance!](#even-more-performance)
+- [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)
+- [Release 2024.4.1 - April 5](#release-202441---april-5)
+- [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=Q1yHfqsVidw)
+3 April 2024, at 20:00 GMT / 12:00 PST / 21:00 CEST!
+
+<lite-youtube videoid="Q1yHfqsVidw" videotitle="Home Assistant 2024.4 Release Party"></lite-youtube>
+
+## Home Assistant spring cleaning! 🧹 New ways to get your automations (and more) organized
+
+By far, the most requested feature in Home Assistant history would be:
+
+[_"Grouping Automations on frontend for organization"_](https://community.home-assistant.io/t/grouping-automations-on-frontend-for-organization/102771).
+
+We hear you! Today, in this release, we are going to give you tools to organize
+your Home Assistant setup, and we took it a few (well, many) steps further than
+just grouping {% term automations %}!
+
+We are introducing 3 (yes, you’ve read it correctly. It’s _three_) organization
+taxonomies, and we revamped our entire table user interface plus a few goodies
+along the way.
+
+## Upgraded tables!
+
+Adding more ways to organize your Home Assistant is great! But being able to
+easily view, filter, and navigate information is just as important. To achieve
+this, we have re-designed ALL the tables in Home Assistant.
+
+For an admin interface, tables are essential for visualizing and managing
+large datasets. Home Assistant has many tables in its settings pages.
+Previously, our UI provided the ability to search, sort, and filter for a few
+aspects, but it was relatively barebones.
+
+Today, we are rolling out a revamped table UI that will be standardized across
+**all** tables in the settings pages with new and improved features.
+
+### A new toolbar
+
+As we add more features to the tables, we need to keep the UI clean and its
+features easy to find. Therefore, we added descriptive text to the dropdown
+menus and standardized the look and feel of the toolbar buttons and text boxes.
+Shiny!
+
+<p class='img'>
+    <img src="/images/blog/2024-04/new-toolbar.png" alt="Screenshots showing the new toolbar that is now on every table in Home Assistant."/>
+    The new toolbar that is now on every table in Home Assistant.
+</p>
+
+### Filter panel
+
+Previously, our automations page allowed you to filter by {% term areas %},
+{% term entities %}, or {% term devices %}, but only one at a time, and the
+filters were tucked away in a dropdown menu, which meant you needed to select
+a dropdown menu inside a dropdown menu to filter by area.
+
+A new filter panel fixes these issues by providing a new dual pane user
+interface that can let you check multiple filters across multiple filter
+types on the left that stay put and view the filtered results on the right.
+
+<img class="no-shadow" src='/images/blog/2024-04/filter-panel.png' alt='Screenshots showing the filter panel that tables can have, allowing you to easily find what you are looking for.'>
+
+We also introduced multiple new filter types for each table. For example,
+{% term automations %} can now be filtered not only by {% term areas %},
+{% term entities %} , or {% term devices %}, but also by used
+{% term blueprints %}, labels, and categories (more on these later!).
+
+We didn’t stop at just that page! The devices and entities pages now also have
+a way to filter not only by state but also by integrations and areas. Almost all
+tables now have useful new filters to help you find what you are looking for.
+
+### Item grouping
+
+Browsing a list of hundreds of {% term automations %} or thousands of 
+{% term entities %} can be overwhelming. While filters can help narrow the list,
+visually grouping the items into smaller chunks makes browsing easier.
+
+With the item grouping feature, we introduced a new dropdown menu to pick
+how you’d like the items on the table to be grouped. On the automations page,
+you can group automations by their {% term state %} - whether enabled
+or not - and custom categories (more on that later!). On the {% term devices %}
+page, you can even group them by manufacturers, {% term areas %},
+or {% term integrations %}, which is really cool because it makes the page much
+easier to browse. It gives you a new perspective on organizing your vast
+network of devices.
+
+<img class="no-shadow" src='/images/blog/2024-04/group-items-by-manufacturer.png' alt='Screenshots showing the devices page, grouped by manufacturer.'>
+
+### Selection mode and batch actions
+
+We removed the clutter of displaying a column of checkboxes by introducing
+a new selection mode. When it is toggled on, checkboxes will appear, and you
+can apply actions to all your selections with one click on the toolbar.
+
+<p class='img'>
+    <img src="/images/blog/2024-04/enable-selection-mode.png" alt="Screenshots point out the enable selection mode button in the toolbar of the tables in Home Assistant."/>
+    This button enables selection mode in the new tables.
+</p>
+
+It allows you to, for example, enable or disable multiple selected
+{% term entities %} on the entities page at once. This new paradigm will allow
+us to introduce more batch management actions in the future.
+
+<img class="no-shadow" src='/images/blog/2024-04/bulk-actions.png' alt='Screenshots showing selection mode active in a table, with some items selected, highlighting the bulk actions you can perform on those selected items.'>
+
+## Three new ways to organize
+
+Upon reading through and ideating on the feature request thread on
+[“Automation Grouping”](https://community.home-assistant.io/t/grouping-automations-on-frontend-for-organization/102771),
+we realized that organization can be done in multiple ways for different purposes.
+
+We learned that users who are proficient in making {% term automations %} have
+hundreds of them, which makes locating a particular automation hard. They often
+had to resort to using "hacks" such as emojis, bracketed “tags”, or numbering
+each automation to get the sort order they wanted. They needed a way to easily
+filter down and break down the giant list into more manageable chunks.
+
+We also noticed that users are stretching our areas feature beyond its
+intended purpose. For example, some users would create “{% term areas %}” such
+as “3D printer”, “Christmas decorations”, or even “Left side of my office desk”,
+to group different {% term devices %} and {% term entities %} together under
+one umbrella for dashboards or {% term automations %}.
+
+As we are developing our new dashboards and voice commands, this poses a
+big problem: We would be unable to provide specialized solutions if a dashboard
+{% term blueprint %} or automation blueprint cannot confidently assume the context of
+how it would be used. We need something more specialized.
+
+Therefore, to balance the basic goal of providing a more digestible UI for
+all users, the need for flexibility for our power users, and the future vision
+of Home Assistant, we are introducing 3 new organization structures to
+Home Assistant:
+
+**[Floors](#floors-help-home-assistant-understand-your-house)**,
+**[Labels](#labels-tag-everything-any-way-you-want)**,
+and **[Categories](#categories-make-each-settings-page-easier-to-browse)**
+
+### Floors: Help Home Assistant understand your house
+
+Let's talk about the new organizational structures, starting with **floors**.
+
+To become a truly intelligent home automation platform, Home Assistant needs
+to understand the context: Where exactly is a {% term device%}? How does one
+{%term area %} relate to another? What is the space used for?
+
+Currently, Home Assistant has {% term areas %}. Areas specify the physical
+location or vicinity of your devices per living space in your home
+(like the living room or kitchen). However, some users living in standalone
+houses might have multiple floors with their own areas.
+
+{% term Floors %} are a new way to organize your areas per level of floors in
+your home. The better Home Assistant knows your home and how it is spatially
+structured, the better it can help you. Especially when it comes to future
+features like generating dashboards, voice commands, and maybe even
+AI-related features.
+
+<img class="no-shadow" src='/images/blog/2024-04/floors.png' alt='Screenshots showing areas settings page, which now also shows the areas grouped by floor.'>
+
+You can use floors in your {% term automations %} and {% term scripts %} as a
+target for your actions or control them with your voice. For example, you can
+turn off all the lights on the downstairs floor when you go to bed or ask
+[Assist](/voice_control/) to turn on the lights upstairs.
+
+For our power users, you can even use [floors in your templates](/docs/configuration/templating/#floors)
+to create the most advanced and creative automations.
+
+{% my areas badge %}
+
+### Labels: Tag everything any way you want
+
+{% term Floors %} and {% term areas %} are great for representing your actual
+home, but as everyone has their own ways of organizing their home, everyone
+has their own ways of organizing their Home Assistant, too!
+This is where **labels** 🏷️ come in!
+
+Labels is an organizational structure that is completely up to you. You can
+make as many labels with any naming structure, in any color 🌈 you want, and
+assign them to basically anything in Home Assistant. You assign labels to
+anything: {% term areas %}, {% term devices %}, {% term entities %},
+{% term automations %}, {% term scripts %}, helpers, you name it!
+You can even assign multiple labels to the same thing.
+
+<img class="no-shadow" src='/images/blog/2024-04/labels.png' alt='Screenshots showing the new labels assigned to automations.'>
+
+Just like with floors, you can use labels in your automations and scripts as
+a target for your {% term actions %}. This gives you a lot of flexibility,
+not just in organizing your Home Assistant, but also in automating your home! 🤯
+
+For example, you could create a label "🎄 Christmas" to label all your
+Christmas decorations during the holiday season. You can then use this label to
+automate all of those decorations at once or to filter them in the new tables.
+
+More examples? You could create a label "🔒 Security" to label and control all
+your security-related devices and automations. Or, "🛌 Bedrooms" to label all
+your bedroom areas and simultaneously control all the devices in those areas.
+
+Do you have solar panels or home batteries? Create a label "⚡️ Heavy energy usage"
+to label devices that consume a lot of energy. You could switch them off when
+there is not enough battery or solar energy available.
+
+You decide how to use labels, and the possibilities are endless! And for our
+power users, you guessed it, you can use [labels in your templates](/docs/configuration/templating/#labels).
+
+{% my labels badge %}
+
+### Categories: Make each settings page easier to browse
+
+Last but not least, we are introducing **categories**. Categories are designed
+to be paired with the aforementioned [item grouping feature](#item-grouping),
+and it can be used to group things visually specific to a certain table
+in Home Assistant.
+
+This is great for those who have a particular way of displaying their
+{% term entities %} by separating them into multiple sections on a specific page.
+For example, on the {% term automations %} page, you can create categories only
+used for visually grouping automations but nowhere else, like "Notifications"
+or “NFC tags”. You can then view your automations grouped or filtered by
+those categories.
+
+<img class="no-shadow" src='/images/blog/2024-04/categories.png' alt='Screenshots the new categories. Automations are grouped into their categories, making it easier to get an overview or to filter them.'>
+
+As these categories are unique for each dashboard, you can have different
+sets of categories depending on the place you are organizing. This means
+you can have different categories on the automations page than the
+{% term scene %}, {% term scripts %}, or helpers settings page.
+
+### Time to clean up your Home Assistant!
+
+In summary, there are a total of 4 taxonomies for organizing your entities.
+It sounds like a lot, but they all serve a distinct purpose. We are extending
+and clarifying {% term areas %} with {% term floors %}, and we are introducing
+{% term labels %} and {% term categories %} to make your {% term automations %}
+and many other tables look more organized and be more manageable.
+
+What’s next? Time to dig in! Here are a few steps we recommend you take
+action on to organize your Home Assistant better:
+
+- **Migrate to labels**:  
+  - If you have been grouping automations with emojis and bracketed text,
+    you can now create labels for each. Labels can have icons to replace the
+    emojis you had before.
+  - For areas that aren’t really physical spaces, switching them to labels will
+    provide you more flexibility in organizing your entities.
+- **Start using categories**:  
+  If you have a favorite way of organizing a particular page, create those
+  categories and group the table by them. For example, you could create a
+  notification category for all your notification automations and put all
+  notification automations in that category.
+- **Group your areas into floors**:  
+  If you live in a multi-story home, grouping areas into floors help with
+  organizing the areas as well as making them more compatible with future
+  features.
+
+Last of all, to help us to help you to perfect the design of these new features,
+we would love to hear your feedback and see how you use them! Please feel free
+to share them in the comments below and discuss them in our community.
+
+## Map dashboard
+
+Introducing a new dashboard this release: The **map**! 🗺️
+
+You might think, "Hey, we already have a map dashboard in Home Assistant!"
+and you are right! However, the map was an integration that was always there
+and didn't provide the flexibility and features that were wanted.
+
+With the map dashboard's introduction, you can now add multiple map dashboards
+with different entities and configuration settings. For example, create a
+dashboard to show the location of your family members, another to track your
+car, and another to show the location of your pets. 🐶
+
+<img class="no-shadow" src='/images/blog/2024-04/dashboard-map.png' alt='Screenshots showing the new map dashboard you can add when you add a new dashboard to your Home Assistant.'>
+
+On upgrade, Home Assistant will automatically migrate your existing map
+integration to a map dashboard.
+
+You don't like having the map in your sidebar? Well, that is no longer a
+problem. Since it is now a dashboard it means you can remove it in the dashboard
+settings.
+
+## Webpage dashboard
+
+Another new dashboard for this release is the **webpage**! 🌐
+
+The webpage dashboard allows you to add and embed a webpage to your dashboard.
+This could be a web page from the internet or a local web page from a local
+machine or device like your router or NAS.
+
+<img class="no-shadow" src='/images/blog/2024-04/dashboard-webpage.png' alt='Screenshots showing addition of a new webpage dashboard to Home Assistant, embedding the Home Assistant website.'>
+
+This dashboard replaces the old iFrame panel (`iframe_panel`). If you have
+existing panels configured in your YAML configuration, Home Assistant will
+automatically migrate them to the new webpage dashboard on upgrade.
+
+<img class="no-shadow" src='/images/blog/2024-04/embedded-home-assistant-website.png' alt='Screenshot showing the Home Assistant website embedded into the Home Assistant frontend using a webpage dashboard.'>
+
+Note that not every webpage can be embedded due to security restrictions that
+some sites or pages have in place, enforced by your browser, that prevent
+embedding them into a Home Assistant dashboard.
+
+## Define the columns in the section view
+
+In the last release, we [introduced the section view](/blog/2024/03/06/release-20243/#a-new-experimental-sections-view)
+with drag and drop support. We are absolutely thrilled to see how many of you
+loved it! 🥰
+
+Many thanks for all the feedback and suggestions! We are prioritizing them and
+are working on making the section view even better in the upcoming releases.
+
+In this release, based on your feedback, we have added the ability for you to
+define the maximum number of columns that the section view uses. This allows you
+to limit the number of columns, regardless of the screen width on which you
+are viewing your dashboard.
+
+<img class="no-shadow" src='/images/blog/2024-04/sections-dashboard-limit-columns.png' alt='Screenshot showing the new option available to limit the number of columns the section view uses.'>
+
+## Adding Matter devices from other controllers
+
+In the [February release](/blog/2024/02/07/release-20242/#matter-diagnostics-and-actions),
+we added support for sharing Matter devices tied to Home Assistant with other
+Matter controllers. This release, we are making the other way around easier.
+
+We have improved how you can add Matter devices from other controllers to
+Home Assistant. When you add a Matter device to Home Assistant, it will now
+ask you if you want to add a new Matter device or if you want to add a device
+that is already added to another controller (like Google Home or Apple Home).
+
+<img class="no-shadow" src='/images/blog/2024-04/add-matter-device.png' alt='Screenshot showing the dialog to add a Matter device, asking if this is a new or existing matter device connected to another controller.'>
+
+Suppose you choose to add a device that has already been added to another
+controller. In that case, Home Assistant will guide you through how to
+achieve this step by step.
+
+<img class="no-shadow" src='/images/blog/2024-04/add-matter-device-from-another-controller.png' alt='Screenshot showing the dialog to add a existing Matter device that is connected to another Matter controller.'>
+
+## Lock behavior improvements
+
+Some smart locks have an open (or unlatching) mechanism that can be triggered
+remotely. The door either pops out of the lock or can be opened by pushing
+against the door.
+
+We want to ensure you don't accidentally open the door when you miss-clicked
+the button (for example, while not at home 😬). Therefore, we have improved
+the behavior of locks in our user interface by requiring you to confirm the
+action.
+
+<img class="no-shadow" src='/images/blog/2024-04/lock-unlatch-confirmation.gif' alt='Screen recording showing the confirmation in the UI when unlatching/opening a door.'>
+
+## Even more performance!
+
+Remember how we wrote last release that [Home Assistant now boots twice as fast](/blog/2024/03/06/release-20243/#home-assistant-boots-twice-as-fast)?
+Well, [@bdraco] wasn't done yet and teamed up with [@balloob]. If you thought
+the previous release was fast, you are in for a treat! 🚀 The difference is,
+yet again, very noticeable.
+
+Besides streamlining what is loaded at startup (and doing less loading), we
+have adjusted the startup time tracking. It used to be that one integration
+could push other integrations to be slow too; that should no longer be the case,
+making this a more accurate representation of the actual startup time.
+
+Want to learn about the individual startup times of your integrations? You can
+find them in the {% my repairs title="**Settings** -> **System** -> **Repairs**" %}
+page by selecting the three-dotted menu in the top right and selecting the
+**Integration startup time** item.
+
+{% my repairs badge %}
+
+[@bdraco]: https://github.com/bdraco
+[@balloob]: https://github.com/balloob
+
+## Other noteworthy changes
+
+There are many more improvements in this release; here are some of the other
+noteworthy changes this release:
+
+- [@karwosts] has improved your Home Assistant {% my profile title="user profile" %}
+  page, making navigating and finding the settings you are looking for easier.
+  Nice work!
+- If you use a [sentence trigger] in your automation to trigger it using
+  [Assist]. The trigger will now include the `device_id` in its trigger data
+  you can automate with. Thanks, [@synesthesiam]!
+- The [HomeWizard Energy] integration now supports the newest generation of
+  HomeWizard Energy Sockets! Thanks, [@DCSBL]!
+- We can now ship new releases of Home Assistant in waaay less time.
+  Building and shipping Home Assistant for you, went down from 1.5-2 hours to
+  just 20 minutes! 🚀 Thanks [@edenhaus]!  
+  [Learn more about it in our developer blog](https://developers.home-assistant.io/blog/2024/04/03/build-images-with-uv/).
+- [Reolink] now supports PTZ patrol start/stop, package detection and controls
+  for playing quick reply messages. Thanks, [@starkillerOG]!
+- We have brand new template functions available to list [all the issues] in
+  your repairs dashboard. Thanks, [@RoboMagus]!
+- If you prefer your wind speed sensors to be in Beaufort, you are in luck!
+  You can now change the unit of measurement to Beaufort. Thanks, [@fwestenberg]!
+- The [Husqvarna Automower] integration development continues and has additional
+  new entities, including sensors, select entities, and a device tracker.
+  Thanks, [@Thomas55555]!
+- [@catsmanac] has added a sensor to monitor the battery storage attached
+  to your [Enphase Envoy]; it works with the energy dashboard! Nice!
+- The [Xiaomi BLE] integration now supports locks and fingerprint readers!
+  Awesome, [@Ernst79]!
+
+[@catsmanac]: https://github.com/catsmanac
+[@DCSBL]: https://github.com/DCSBL
+[@edenhaus]: https://github.com/edenhaus
+[@Ernst79]: https://github.com/Ernst79
+[@fwestenberg]: https://github.com/fwestenberg
+[@karwosts]: https://github.com/karwosts
+[@RoboMagus]: https://github.com/RoboMagus
+[@starkillerOG]: https://github.com/starkillerOG
+[@synesthesiam]: https://github.com/synesthesiam
+[@Thomas55555]: https://github.com/Thomas55555
+[all the issues]: /docs/configuration/templating/#issues
+[Assist]: /voice_control/
+[Enphase Envoy]: /integrations/enphase_envoy
+[HomeWizard Energy]: /integrations/homewizard
+[Husqvarna Automower]: /integrations/husqvarna_automower
+[Reolink]: /integrations/reolink
+[sentence trigger]: /docs/automation/trigger/#sentence-trigger
+[Xiaomi BLE]: /integrations/xiaomi_ble
+
+## New integrations
+
+We welcome the following new integrations in this release:
+
+- **[Fyta]**, added by [@dontinelli]<br />
+  Monitor your plants with Fyta, a smart plant sensor that measures light,
+  temperature, humidity, and soil moisture.
+- **[Motionblinds Bluetooth]**, added by [@LennP]<br />
+  Control your Bluetooth Low Energy Motionblinds motorized window coverings.
+- **[Ollama]**, added by [@synesthesiam]<br />
+  Ollama a fully local AI conversation platform that can be used to create
+  custom voice assistants.
+
+[@dontinelli]: https://github.com/dontinelli
+[@LennP]: https://github.com/LennP
+[@synesthesiam]: https://github.com/synesthesiam
+[Fyta]: /integrations/fyta
+[Motionblinds Bluetooth]: /integrations/motionblinds_ble
+[Ollama]: /integrations/ollama
+
+This release also has new virtual integration. Virtual integrations are stubs
+that are handled by other (existing) integrations to help with findability.
+The following virtual integration have been added:
+
+- **[Sacramento Municipal Utility District (SMUD)]**, provided by [Opower]
+
+[Sacramento Municipal Utility District (SMUD)]: /integrations/smud
+[Opower]: /integrations/opower
+
+## Integrations now available to set up from the UI
+
+The following integrations are now available via the Home Assistant UI:
+
+- **[Lutron Homeworks]**, done by [@emontnemery]
+- **[17TRACK]**, done by [@shaiu]
+- **[Downloader]**, done by [@erwindouna]
+- **[ROVA]**, done by [@GidoHakvoort]
+
+[@emontnemery]: https://github.com/emontnemery
+[@erwindouna]: https://github.com/erwindouna
+[@GidoHakvoort]: https://github.com/GidoHakvoort
+[@shaiu]: https://github.com/shaiu
+[17TRACK]: /integrations/seventeentrack
+[Downloader]: /integrations/downloader
+[Lutron Homeworks]: /integrations/homeworks
+[ROVA]: /integrations/rova
+
+## Release 2024.4.1 - April 5
+
+- Update aioairzone-cloud to v0.4.7 ([@Noltari] - [#114761])
+- Bump myuplink dependency to 0.6.0 ([@astrandb] - [#114767])
+- Update romy to 0.0.9 ([@cdce8p] - [#114360])
+- Update romy to 0.0.10 ([@xeniter] - [#114785])
+- Fix unhandled `KeyError` during Notion setup ([@bachya] - [#114787])
+- Fix Lutron light brightness values ([@cdheiser] - [#114794])
+- Fix type cast in snmp ([@lextm] - [#114795])
+- Handle ambiguous script actions by using action map order ([@bdraco] - [#114825])
+- Bump opower to 0.4.3 ([@tronikos] - [#114826])
+- Refactor ConfigStore to avoid needing to pass config_dir ([@bdraco] - [#114827])
+- Avoid blocking IO in downloader initialization ([@joostlek] - [#114841])
+- Fix Downloader YAML import ([@joostlek] - [#114844])
+- Update frontend to 20240404.0 ([@bramkragten] - [#114859])
+- Fix Axis camera platform support HTTPS ([@Kane610] - [#114886])
+- Bump weatherflow4py to 0.2.20 ([@jeeftor] - [#114888])
+- Fix Axis reconfigure step not providing protocols as alternatives but as string ([@Kane610] - [#114889])
+- Update frontend to 20240404.1 ([@bramkragten] - [#114890])
+- Ensure all tables have the default table args in the db_schema ([@bdraco] - [#114895])
+- Reduce august polling frequency ([@bdraco] - [#114904])
+- Show correct model string in myuplink ([@astrandb] - [#114921])
+- Create right import issues in Downloader ([@joostlek] - [#114922])
+- Fix cast dashboard in media browser ([@joostlek] - [#114924])
+- Pin systembridgemodels to 4.0.4 ([@timmo001] - [#114842])
+- Fix ROVA validation ([@joostlek] - [#114938])
+
+[#114360]: https://github.com/home-assistant/core/pull/114360
+[#114761]: https://github.com/home-assistant/core/pull/114761
+[#114764]: https://github.com/home-assistant/core/pull/114764
+[#114767]: https://github.com/home-assistant/core/pull/114767
+[#114785]: https://github.com/home-assistant/core/pull/114785
+[#114787]: https://github.com/home-assistant/core/pull/114787
+[#114794]: https://github.com/home-assistant/core/pull/114794
+[#114795]: https://github.com/home-assistant/core/pull/114795
+[#114825]: https://github.com/home-assistant/core/pull/114825
+[#114826]: https://github.com/home-assistant/core/pull/114826
+[#114827]: https://github.com/home-assistant/core/pull/114827
+[#114841]: https://github.com/home-assistant/core/pull/114841
+[#114842]: https://github.com/home-assistant/core/pull/114842
+[#114844]: https://github.com/home-assistant/core/pull/114844
+[#114859]: https://github.com/home-assistant/core/pull/114859
+[#114886]: https://github.com/home-assistant/core/pull/114886
+[#114888]: https://github.com/home-assistant/core/pull/114888
+[#114889]: https://github.com/home-assistant/core/pull/114889
+[#114890]: https://github.com/home-assistant/core/pull/114890
+[#114895]: https://github.com/home-assistant/core/pull/114895
+[#114904]: https://github.com/home-assistant/core/pull/114904
+[#114921]: https://github.com/home-assistant/core/pull/114921
+[#114922]: https://github.com/home-assistant/core/pull/114922
+[#114924]: https://github.com/home-assistant/core/pull/114924
+[#114938]: https://github.com/home-assistant/core/pull/114938
+[@Kane610]: https://github.com/Kane610
+[@Noltari]: https://github.com/Noltari
+[@astrandb]: https://github.com/astrandb
+[@bachya]: https://github.com/bachya
+[@bdraco]: https://github.com/bdraco
+[@bramkragten]: https://github.com/bramkragten
+[@cdce8p]: https://github.com/cdce8p
+[@cdheiser]: https://github.com/cdheiser
+[@frenck]: https://github.com/frenck
+[@jeeftor]: https://github.com/jeeftor
+[@joostlek]: https://github.com/joostlek
+[@lextm]: https://github.com/lextm
+[@timmo001]: https://github.com/timmo001
+[@tronikos]: https://github.com/tronikos
+[@xeniter]: https://github.com/xeniter
+
+## 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 "Python 3.11 support has been removed" %}
+
+Python 3.11 support has previously been deprecated and has now been removed.
+Home Assistant now requires Python 3.12 to run.
+
+You don’t have to do anything if you are using the Home Assistant Operating
+System, Home Assistant Container, or Home Assistant Supervised installation
+method. In those cases, we handle all of this for you. Your system has been
+using Python 3.12 for quite some time already.
+
+([@frenck] - [#114220])
+
+[@frenck]: https://github.com/frenck
+[#114220]: https://github.com/home-assistant/core/pull/114220
+
+{% enddetails %}
+
+{% details "AEMET OpenData" %}
+
+The AEMET OpenData integration previously created two entities for each
+configured location: one provided daily weather forecasts and the other hourly
+forecasts.
+
+The AEMET OpenData integration now only creates a single entity that provides
+both daily and hourly weather forecasts.
+
+([@gjohansson-ST] - [#110764]) ([documentation](/integrations/aemet))
+
+[@gjohansson-ST]: https://github.com/gjohansson-ST
+[#110764]: https://github.com/home-assistant/core/pull/110764
+
+{% enddetails %}
+
+{% details "Dexcom" %}
+
+The trend sensor now uses values that are using snake_case instead of a space
+in the middle:
+
+- `rising quickly` -> `rising_quickly`
+- `rising slightly` -> `rising_slightly`
+- `falling slightly` -> `falling_slightly`
+- `falling quickly` -> `falling_quickly`
+
+Please update your automations and scripts accordingly.
+
+([@joostlek] - [#112423]) ([documentation](/integrations/dexcom))
+
+[@joostlek]: https://github.com/joostlek
+[#112423]: https://github.com/home-assistant/core/pull/112423
+
+{% enddetails %}
+
+{% details "ecobee" %}
+
+The non-functional `away` preset mode has been replaced with the correct
+`away_indefinitely` preset mode.
+
+If any automation or script depends on the `away` preset mode,
+it needs to be updated.
+
+([@alexsydell] - [#108636]) ([documentation](/integrations/ecobee))
+
+[@alexsydell]: https://github.com/alexsydell
+[#108636]: https://github.com/home-assistant/core/pull/108636
+
+{% enddetails %}
+
+{% details "Environment Canada" %}
+
+The Environment Canada integration previously created two entities for each
+configured location: one provided daily weather forecasts and the other hourly
+forecasts.
+
+The Environment Canada integration now only creates a single entity that
+provides both daily and hourly weather forecasts.
+
+([@gjohansson-ST] - [#112447]) ([documentation](/integrations/environment_canada))
+
+[@gjohansson-ST]: https://github.com/gjohansson-ST
+[#112447]: https://github.com/home-assistant/core/pull/112447
+
+{% enddetails %}
+
+{% details "National Weather Service (NWS)" %}
+
+The National Weather Service integration previously created two entities for each
+configured location: one provided daily weather forecasts and the other hourly
+forecasts.
+
+The National Weather Service integration now only creates a single entity that
+provides both daily and hourly weather forecasts.
+
+([@gjohansson-ST] - [#112503]) ([documentation](/integrations/nws))
+
+[@gjohansson-ST]: https://github.com/gjohansson-ST
+[#112503]: https://github.com/home-assistant/core/pull/112503
+
+{% enddetails %}
+
+{% details "Met Éireann" %}
+
+The Met Éireann integration previously created two entities for each configured
+location: one provided daily weather forecasts and the other hourly forecasts.
+
+The Met Éireann integration now only creates a single entity that provides both
+daily and hourly weather forecasts.
+
+([@gjohansson-ST] - [#112449]) ([documentation](/integrations/met_eireann))
+
+[@gjohansson-ST]: https://github.com/gjohansson-ST
+[#112449]: https://github.com/home-assistant/core/pull/112449
+
+{% enddetails %}
+
+{% details "Met Office" %}
+
+The Met Office integration previously created two entities for each configured
+location: one provided daily weather forecasts and the other hourly forecasts.
+
+The Met Office integration now only creates a single entity that provides both
+daily and hourly weather forecasts.
+
+([@gjohansson-ST] - [#112452]) ([documentation](/integrations/metoffice))
+
+[@gjohansson-ST]: https://github.com/gjohansson-ST
+[#112452]: https://github.com/home-assistant/core/pull/112452
+
+{% enddetails %}
+
+{% details "Modbus" %}
+
+The Modbus integration does not allow a configuration with the device only
+(no entities); this will create an issue, and the entry will not be loaded.
+
+For the special cases (like some custom_components) where it is wanted,
+please add a dummy entity.
+
+([@janiversen] - [#113516]) ([documentation](/integrations/modbus))
+
+[@janiversen]: https://github.com/janiversen
+[#113516]: https://github.com/home-assistant/core/pull/113516
+
+{% enddetails %}
+
+{% details "MQTT" %}
+
+Support for `brightness` is now assumed for `mqtt` lights with the `json` schema
+unless only color modes `rgb`, `rgbw`, or `rgbww` are supported.
+
+For lights which only support  color modes `rgb`, `rgbw`, or `rgbww`, 
+the `brightness` option flag can still be set to `false` if brightness is not
+supported. In this case brightness support is emulated in Home Assistant by
+scaling the RGBx-values.
+
+For all other color modes except `ColorMode.ONOFF`, it is assumed brightness is
+supported, and the `brightness` attribute will be included in the MQTT payload
+when the `brightness` attribute is supplied to the `light.turn_on` service.
+
+([@jbouwh] - [#111676]) ([documentation](/integrations/mqtt))
+
+[@jbouwh]: https://github.com/jbouwh
+[#111676]: https://github.com/home-assistant/core/pull/111676
+
+{% enddetails %}
+
+{% details "myUplink" %}
+
+If you have a Nibe SMO 20 in your account, you will notice that some 550
+entities are no longer provided by the integration.
+
+You can safely remove these entities as the integration does not use them.
+
+([@astrandb] - [#113493]) ([documentation](/integrations/myuplink))
+
+[@astrandb]: https://github.com/astrandb
+[#113493]: https://github.com/home-assistant/core/pull/113493
+
+{% enddetails %}
+
+{% details "Waze Travel Time" %}
+
+The options `excl_filter` and `incl_filter` now filter for exact matches to
+street names in the route. Previously, they only filtered on the short
+description of the route.
+
+([@eifinger] - [#108613]) ([documentation](/integrations/waze_travel_time))
+
+[@eifinger]: https://github.com/eifinger
+[#108613]: https://github.com/home-assistant/core/pull/108613
+
+{% enddetails %}
+
+{% details "Weather" %}
+
+The previously deprecated `forecast` attribute of weather entities, has now been
+removed. Use the [`weather.get_forecasts`](/integrations/weather#service-weatherget_forecasts)
+service to get the forecast data instead.
+
+([@gjohansson-ST] - [#110761]) ([documentation](/integrations/metoffice))
+
+[@gjohansson-ST]: https://github.com/gjohansson-ST
+[#110761]: https://github.com/home-assistant/core/pull/110761
+
+{% 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:
+
+- [Climate entity auxiliary heater is deprecated](https://developers.home-assistant.io/blog/2024/03/10/climate-aux-heater-deprecated)
+- [Config Entries can now provide a reconfigure step](https://developers.home-assistant.io/blog/2024/03/21/config-entry-reconfigure-step)
+- [Deprecate hass.helpers usage](https://developers.home-assistant.io/blog/2024/03/30/deprecate-hass-helpers/)
+- [Deprecating `async_run_job` and `async_add_job`](https://developers.home-assistant.io/blog/2024/03/13/deprecate_add_run_job)
+- [How uv saves Home Assistant 215 compute hours per month](https://developers.home-assistant.io/blog/2024/04/03/build-images-with-uv/)
+- [Integrations import in the executor to avoid blocking the event loop](https://developers.home-assistant.io/blog/2024/03/09/import_executor_default)
+- [New state timestamp State.last_reported](https://developers.home-assistant.io/blog/2024/03/20/state_reported_timestamp)
+- [Raising exceptions with translations](https://developers.home-assistant.io/blog/2024/03/15/exception-translations)
+
+[devblog]: https://developers.home-assistant.io/blog/
+
+## Farewell to the following
+
+The following integrations are also no longer available as of this release:
+
+- **OpenCV** has been removed. The integration has been in a broken state
+  for over a year and currently has no path forward.
+  ([@thecode] - [#113455])
+
+[@thecode]: https://github.com/thecode
+[#113455]: https://github.com/home-assistant/core/pull/113455
+
+## 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 2024.4](/changelogs/core-2024.4)

source/dashboards/cards.markdown

@@ -25,7 +25,7 @@ There are several different card types, each with their own configuration option
 
 Some cards have support for [tap actions](/dashboards/actions/). These actions define what will happen when you tap or hold on an object within a card.
 
-Some cards have support for [features](/dashboards/actions/). These widgets add quick controls to the card. Supported features depend on the card and entity capabilities. Multiple features can be added to a single card.
+Some cards have support for [features](/dashboards/features/). These widgets add quick controls to the card. Supported features depend on the card and entity capabilities. Multiple features can be added to a single card.
 
 <p class='img'><img src='/images/dashboards/features/screenshot-tile-feature-grid.png' alt="Screenshot of tile cards with features.">
 Screenshot of tile cards with features.
@@ -87,4 +87,4 @@ Another way to add entities to a dashboard is to use the **Device** page.
 - For a list of available card types and more detailed documentation, refer to the **Card types** section in the side navigation.
 - [Card tap actions](/dashboards/actions/)
 - [Card features](/dashboards/actions/)
-- [Card header and footer widgets](/dashboards/header-footer/)
+- [Card header and footer widgets](/dashboards/header-footer/)

source/dashboards/header-footer.markdown

@@ -13,7 +13,7 @@ Header and footer can be used on the following cards:
 
 - [Entity](/dashboards/entity/)
 - [Entities](/dashboards/entities/)
-- [Statictis](/dashboards/statistics/)
+- [Statistics](/dashboards/statistics/)
 
 ## Picture header & footer
 
@@ -151,5 +151,5 @@ hours_to_show:
 
 - [Entity](/dashboards/entity/)
 - [Entities](/dashboards/entities/)
-- [Statictis](/dashboards/statistics/)
-- [Card actions](/dashboards/actions/)
+- [statistics](/dashboards/statistics/)
+- [Card actions](/dashboards/actions/)

source/voice_control/aliases.markdown

@@ -1,8 +1,8 @@
 ---
-title: "Assist - entity and area aliases"
+title: "Assist - entity, area, and floor aliases"
 ---
 
-Assist will use the names of your entities and areas, as well as any aliases you've configured. The configured aliases are not only used by Assist, but can also be used by Google Assistant, if you have set that up.
+Assist will use the names of your entities, areas and floors, as well as any aliases you've configured. The configured aliases are not only used by Assist, but can also be used by Google Assistant, if you have set that up.
 
 These aliases are helpful in case you call the same device by multiple names
 or when using a voice assistant in multiple languages at the same time.
@@ -18,7 +18,20 @@ There are multliple ways to add an alias of an entity:
 
 ## Adding an alias of an area
 
-1. To add an alias for an area, go to {% my zones title="**Settings** > **Areas, labels & zones**" %}.
-2. Select the area of interest.
-3. In the three-dot menu, select **Area settings**.
-4. Select **Add alias** and enter the alias you want to use for that area.
+1. To add an alias for an area, go to **Settings** > **Areas, labels & zones**.
+2. On the area card of interest, select the pencil button.
+3. Select **Add alias** and enter the alias you want to use for that area.
+4. **Save** your changes.
+
+## Adding an alias of a floor
+
+1. To add an alias for a floor, go to **Settings** > **Areas, labels & zones**.
+2. Next to the floor of interest, select the three-dot menu, then select **Edit floor**.
+3. Select **Add alias** and enter the alias you want to use for that floor.
+4. **Save** your changes.
+
+## Related topics
+
+- [Areas](/docs/organizing/areas/)
+- [Floors](/docs/organizing/floors/)
+- [Assist - custom sentences](/voice_control/custom_sentences/)