2024.3: Beta release notes (#31584)

* 2024.3: Beta release notes

* Tiny fixes

* Add script fields

* Dont use heading as it messes with toc

* Add new energy graph

* update

* Update 2024-03-06-release-20243.markdown

---------

Co-authored-by: Paulus Schoutsen <balloob@gmail.com>
Co-authored-by: Paul Bottein <paul.bottein@gmail.com>
Co-authored-by: Bram Kragten <mail@bramkragten.nl>

_config.yml

@@ -109,9 +109,9 @@ social:
 
 # Home Assistant release details
 current_major_version: 2024
-current_minor_version: 2
-current_patch_version: 5
-date_released: 2024-02-27
+current_minor_version: 3
+current_patch_version: 0
+date_released: 2024-03-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.

source/_posts/2024-03-06-release-20243.markdown

@@ -0,0 +1,363 @@
+---
+layout: post
+title: "2024.3: Beta release notes"
+description: "The beta release notes for Home Assistant 2024.3"
+date: 2024-02-28 00:00:00
+date_formatted: "March 6, 2024"
+author: Franck Nijhof
+author_twitter: frenck
+comments: true
+categories:
+  - Release-Notes
+  - Core
+og_image: /images/blog/2024-03/social.png
+---
+
+<a href='/integrations/#version/2024.3'><img src='/images/blog/2024-03/social.png' style='border: 0;box-shadow: none;'></a>
+
+<!-- BELOW NEEDS TO BE REMOVED BEFORE THE RELEASE -->
+
+These are the beta release notes for Home Assistant Core 2024.2 (and is thus a
+work in progress).
+
+If you encounter any issues with the beta release, please report them on GitHub:
+
+- Issues with integrations, automations and such (Core related):<br>
+  <https://github.com/home-assistant/core/issues>
+- Issues with the frontend/UI/dashboards:<br>
+  <https://github.com/home-assistant/frontend/issues>
+- Issues with the documentation:<br>
+  <https://github.com/home-assistant/home-assistant.io/issues>
+
+Please be sure to include the beta version you are running in the issue
+version field (not title), so we can classify your issue correctly.
+
+Issues introduced in the beta are processed with priority.
+
+---
+
+<!-- ABOVE NEEDS TO BE REMOVED BEFORE THE RELEASE -->
+
+Home Assistant Core 2024.3! 🎉
+
+Thanks for helping out testing the beta! ❤️
+
+Enjoy the (beta) release!
+
+../Frenck
+
+<!--more-->
+
+- [Dashboard sections view](#dashboard-sections-view)
+- [Dungeons and Dragons](#dungeons-and-dragons)
+- [Running script from your dashboard with user input](#running-script-from-your-dashboard-with-user-input)
+- [New energy graph](#new-energy-graph)
+- [New sentences for Assist](#new-sentences-for-assist)
+- [Disabling the remotely enabling of Home Assistant Remote UI](#disabling-the-remotely-enabling-of-home-assistant-remote-ui)
+- [Translating states in your templates](#translating-states-in-your-templates)
+- [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)
+- [All changes](#all-changes)
+
+Don't forget to [join our release party live stream on YouTube](https://www.youtube.com/watch?v=Jxup-fKFpfs)
+6 March 2024, at 20:00 GMT / 12:00 PST / 21:00 CET!
+
+<lite-youtube videoid="Jxup-fKFpfs" videotitle="Home Assistant 2024.3 Release Party"></lite-youtube>
+
+## Dashboard sections view
+
+A brand new, experimental, view has been added this release: Sections!
+
+<img class="no-shadow" src='https://github.com/home-assistant/frontend/assets/5878303/d1b9f4d8-3d00-42a1-8479-0363e3b740e6' alt='Temporary image that needs replacement.'>
+
+## Dungeons and Dragons
+
+Lorem ipsum
+
+## Running script from your dashboard with user input
+
+Scripts in Home Assistant allow you to capture a sequence of actions and choices in a reusable way. Scripts are extra powerful because they can have input fields, which allow you to send in data for when the script runs.
+
+Script fields can be defined in the script editor and show up when you call the script in your automation. In this release, script fields will be available in the more info dialog when tapping on a script in the dashboard. This allows you to provide the input fields and run the script, unlocking a whole new dimension of possibilities.
+
+<lite-youtube videoid="mTan5y7Ed58" videotitle="Calling scripts from the dashboard"></lite-youtube>
+
+To accompany this new functionality, we've created two blueprints that you can use to add to your dashboard:
+
+**Broadcast message**
+
+This blueprint allows you to create a script that broadcasts a Text-to-Speech message to specific media players and asks the user for the message to broadcast.
+
+{% my blueprint_import badge blueprint="https://example.com" %}
+
+**Add to to-do list**
+
+This blueprint allows you to create a script to quickly add a task to a to-do list.
+
+{% my blueprint_import badge blueprint="https://example.com" %}
+
+## New energy graph
+
+A new graph has been added on the energy dashboard by [@karwosts]. You can now monitor your devices energy consumption through time.
+
+<img class="no-shadow" src='https://github.com/home-assistant/frontend/assets/5878303/47c83332-aa7d-424a-bd00-6ed23b11f000' alt='Temporary image that needs replacement.'>
+
+
+## New sentences for Assist
+
+Assists has been expanded with new intent sentences, allowing you to control
+even more devices and services.
+
+Support for valves has been added. You can now ask it to adjust the position
+of a valve to, for example, 50%, or just open or close a valve completely.
+
+Covers support has been extended, and it now can control the position of
+covers, for example, "open the blinds 50%".
+
+No need to worry if you found a dusty spot in your home, starting the vacuum
+is now also a new capability. Or, in case you are annoyed by the noise of the
+vacuum, you can also ask it to return to base.
+
+The biggest set of changes is for media players. You can now ask it to play,
+pause, unpause, and to fast-forward to the next item. But not just that, you
+can also control the volume.
+
+## Disabling the remotely enabling of Home Assistant Remote UI
+
+If you are using [Home Assistant Cloud](https://nabucasa.com), you can access
+your Home Assistant instance remotely using the Remote UI feature.
+
+If this feature is for some reason disabled and you are currently not at home,
+you can enable the Remote UI feature remotely, by logging in into your [Nabu Casa
+account](https://account.nabucasa.com/), and request your Home Assistant instance to turn it on.
+
+Feedback from the community has shown that this feature is not always desired,
+and this release adds a new option to disable the remotely enabling of the
+Remote UI feature.
+
+## Translating states in your templates
+
+Are you using templates to send notification in automations? If so,
+[@PiotrMachowski] might just have added something you need this release!
+
+He added a new template methods to translate entity states right in your
+templates! Here is an example:
+
+{% raw %}
+```yaml
+# Untranslated
+{{ states("binary_sensor.movement_backyard") }}  # Shows: on
+{{ states("sun.sun") }}  # Shows: below_horizon
+```
+{% endraw %}
+
+The above two example, show the raw state of the entities. However, with the
+new `state_translated` method, you can get the state in a human readable form:
+
+{% raw %}
+```yaml
+# Translated
+{{ state_translated("binary_sensor.movement_backyard") }}  # Shows: Detected
+{{ state_translated("sun.sun") }}  # Shows: Below horizon
+```
+{% endraw %}
+
+Even better, it uses the default language of your Home Assistant instance. So,
+if you are using Home Assistant in a different language, the translated state
+will be in that language.
+
+[@PiotrMachowski]: https://github.com/PiotrMachowski
+
+## Other noteworthy changes
+
+There are many more improvements in this release; here are some of the other
+noteworthy changes this release:
+
+- Lorem ipsum, thanks [@frenck]!
+
+[@frenck]: https://github.com/frenck
+
+_Note to remove: Processed possible noteworthy up to PR #111092_
+
+Marked noteworhy from Core:
+
+- Add Charging sensor to Tessie ([@Bre77] - [#108205]) ([tessie docs]) (noteworthy)
+- Add Speed Limit to Tessie lock platform ([@Bre77] - [#106527]) ([tessie docs]) (noteworthy)
+- Add transition support to Matter light platform ([@marcelveldt] - [#109803]) ([matter docs]) (noteworthy)
+- Add update platform to myuplink ([@astrandb] - [#109786]) ([myuplink docs]) (new-platform) (noteworthy)
+- Add setpoints for fans to flexit_bacnet ([@lellky] - [#110262]) ([flexit_bacnet docs]) (new-platform) (noteworthy)
+- Add media file playback to DuneHD ([@iliessens] - [#105796]) ([dunehd docs]) (noteworthy)
+- Add toggle service to climate ([@arturpragacz] - [#100418]) ([climate docs]) (noteworthy)
+- Add new range sensors to Tessie ([@Bre77] - [#110446]) ([tessie docs]) (noteworthy)
+- Support Bring! recently list ([@miaucl] - [#109854]) ([bring docs]) (noteworthy)
+
+Marked noteworthy from Frontend:
+
+- Add devices to energy collection (#19849) @karwosts
+
+## New integrations
+
+We welcome the following new integrations in this release:
+
+- **[Aprilaire]**, added by [@chamberlain2007]<br />
+  TODO: Description
+- **[Husqvarna Automower]**, added by [@Thomas55555]<br />
+  The Husqvarna Automower integration allows you to integrate and control
+  lawn mower straight from Home Assistant.
+- **[microBees]**, added by [@marcolettieri]<br />
+  TODO: Description
+
+[@chamberlain2007]: https://github.com/chamberlain2007
+[@marcolettieri]: /integrations/marcolettieri
+[@Thomas55555]: https://github.com/Thomas55555
+[Aprilaire]: /integrations/aprilaire
+[Husqvarna Automower]: /integrations/husqvarna_automower
+[microBees]: /integrations/microbees
+
+This release also has new virtual integrations. Virtual integrations are stubs
+that are handled by other (existing) integrations to help with findability.
+The following virtual integrations have been added:
+
+- **[Duquesne Light]**, provided by [Opower]
+- **[SamSam]**, provided by [EnergyZero]
+- **[ZonderGas]**, provided by [EnergyZero]
+
+[Duquesne Light]: /integrations/duquesne_light
+[EnergyZero]: /integrations/energyzero
+[Opower]: /integrations/opower
+[SamSam]: /integrations/samsam
+[ZonderGas]: /integrations/zondergas
+
+## Integrations now available to set up from the UI
+
+The following integrations are now available via the Home Assistant UI:
+
+- **[Velux]**, done by [@DeerMaximum]
+
+[@DeerMaximum]: https://github.com/DeerMaximum
+[Velux]: /integrations/velux
+
+## 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 "AEMET" %}
+
+The daily data for the current day wasn't available after midday and
+now it will be. Automations and script relying on `day[0]` for checking
+next day forecast will have to be adjusted to use `day[1]` instead.
+
+([@Noltari] - [#107795]) ([documentation](/integrations/aemet))
+
+[@Noltari]: https://github.com/Noltari
+[#107795]: https://github.com/home-assistant/core/pull/107795
+
+{% enddetails %}
+
+{% details "JuiceNet" %}
+
+The JuiceNet integration has been removed.
+
+Enel X has migrated from JuiceNet to JuicePass rendering the JuiceNet integration useless. Background and alternative solutions to the juicenet integration can be found in the related [issue](https://github.com/home-assistant/core/issues/86588).
+
+([@emontnemery] - [#111477])
+
+[#111477]: https://github.com/home-assistant/core/pull/111477
+
+{% enddetails %}
+
+{% details "Met.no" %}
+
+The met.no integration previously created two entities for each configured
+location, one entity which provided daily weather forecasts and one entity
+which provided hourly forecasts.
+
+The met.no integration now only creates a single entity which provides
+both daily and hourly weather forecasts.
+
+([@emontnemery] - [#97023]) ([documentation](/integrations/met))
+
+[@emontnemery]: https://github.com/emontnemery
+[#97023]: https://github.com/home-assistant/core/pull/97023
+
+{% enddetails %}
+
+{% details "MQTT" %}
+
+Aux heat, which was deprecated in Home Assistant Core 2023.9,
+is now removed from MQTT climate.
+
+([@jbouwh] - [#109513]) ([documentation](/integrations/mqtt))
+
+[@jbouwh]: https://github.com/jbouwh
+[#109513]: https://github.com/home-assistant/core/pull/109513
+
+{% enddetails %}
+
+{% details "Z-Wave" %}
+
+For Z-Wave `climate` entities, the behavior of the `climate.turn_on` service
+has changed. Previously, the service would act in the following order depending
+on whether the corresponding conditions were met:
+
+1. If the entity supported the `off` mode and exactly one additional mode,
+   `climate.turn_on` would set the mode to the additional mode.
+2. If conditions for 1 were not met and at least one of the following modes is
+   available, the service would set the mode to the first mode it found
+   in specified order: `heat_cool`, `heat`, `cool`.
+3. If conditions for 1 and 2 were not met, the service would silently do nothing.
+
+Now, the service follows the following behavior in order:
+
+1. If the entity supports the `resume` thermostat mode, it will be used to
+   restore the last mode you used before the entity was turned off.
+2. If the condition for 1 isn't met and the entity was turned off in
+   Home Assistant, and Home Assistant wasn't restarted, Home Assistant
+   remembers the last "on" mode and will set it to that mode. Home Assistant
+   will be unable to set the entity to the previous mode if Home Assistant
+   starts with the entity already in `off` mode since the integration will
+   not know what the previous mode was.
+3. If conditions for 1 and 2 are not met and at least one of the following
+   modes is available, the service sets the mode to the first mode it finds
+   in specified order: `heat_cool`, `heat`, `cool`
+   (no change to condition 2 above).
+4. If conditions for 1, 2, and 3 are not met, the mode will be set to the first
+   supported mode it finds (e.g. `dry` or `fan_only`).
+
+([@raman325] - [#109187]) ([documentation](/integrations/zwave_js))
+
+[@raman325]: https://github.com/raman325
+[#109187]: https://github.com/home-assistant/core/pull/109187
+
+{% 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:
+
+- [Altering config entries](https://developers.home-assistant.io/blog/2024/02/12/async_update_entry/)
+- [It is now required for lights to set color mode](https://developers.home-assistant.io/blog/2024/02/12/light-color-mode-mandatory/)
+
+[devblog]: https://developers.home-assistant.io/blog/
+
+## 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.3](/changelogs/core-2024.3)