2024.3: Drag ‘n Drop it prefer it’s scorching! 🎉

Dwelling Assistant Core 2024.3! 🎉

Sure, you learn the title proper! I’m tremendous stoked about this one. It has been
talked about for ages… I promise it’s actual:

Drag ’n drop for dashboards is lastly right here! 🎉

A primary experimental model of the part dashboard that helps drag ’n drop.
An incredible step ahead and a good larger milestone for Dwelling Assistant!

However don’t be blinded by these Dungeons ’n Dragons; there may be much more!

New intents for Help (I can lastly inform my vacuum to begin cleansing!), utilizing
script inputs/fields from the dashboard, and a brand new vitality graph for particular person
units. And that’s simply the tip of the iceberg!

Benefit from the launch!


PS: A giant thanks and shoutout to @bramkragten & @balloob for organizing
and working the beta and everybody who helped out making these launch notes
occur throughout my absence this beta. 🥰

Don’t overlook to join our release party live stream on YouTube
6 March 2024, at 20:00 GMT / 12:00 PST / 21:00 CET!

A brand new experimental sections view

Our dashboard at the moment comes with three view format varieties:
Panel, Sidebar,
and Masonry. Since the past year, we have been working
hard to research and ideate on how to make dashboards easier to customize
and use, and we learned that our current layouts are not the best for such
purposes. Drag-and-drop rearrangement of cards cannot work well with the
Masonry layout.

We came up with a few solutions, and the first thing we would like to share
with you is a new view layout type called “Sections”.

Home Assistant dashboards are robust and packed with information. Users will
often place dozens of cards for all sorts of buttons, switches, graphs,
indicators, and more.

Example of a dashboard section
Example of a dashboard section

By grouping cards into “sections”, you can reduce the number of items you
need to scan through when you are looking for a certain card, as you’ll be
able to look for the relevant group title first and then reduce the scope to
scan that particular group for the information.

By packing cards in a section into a grid with a fixed number of columns,
the relative positions of the cards within a section are not affected by
changes in screen sizes, and so the spatial memory of the cards is retained,
leading to a faster and less cumbersome experience.

A fully populated dashboard in Sections view layout
A fully populated dashboard in the Sections view layout

Cards in the new sections view type are all aligned in a tidy grid to ensure
consistency and predictability of their positions when the screen size changes.
We currently have three cards reworked to fit the grid:
Tile, Sensor,
and Button cards. These cards will occupy the right
amount of space in the grid, while other cards will occupy the full width
of a section by default at the moment. Moreover, we have tweaked our
“Add Cards” dialogs to recommend Tile cards by default when the sections
view type is in use.

The new Sections view is experimental! Please do not build your daily dashboard on top of it yet! We are releasing this early so that we can collect your feedback.

To get started with the new Sections view type, create a new view on your
dashboard and select Sections (experimental) as the view type.
We currently do not have the option to migrate your current dashboard over yet.

For more information, check out our blog post about our new
series A Home-Approved Dashboard: Chapter 1.

Amazing work! Thanks Paul,
and Madelena!

Drag-and-drop rearrangement of cards and sections!

Wow! At long last!! The stars have aligned, and our experimental drag-and-drop
feature for dashboards is finally here! 🥲

With the new sections view type, we can finally implement a way to arrange
cards and sections that is intuitive with drag-and-drop gestures and predictable
with how the cards will rearrange while creating a dashboard that is easy to
navigate and remember. You will no longer need to pray and guess where the cards
will land when they change their order!

How to drag and drop

While your dashboard is in edit mode:

Rearranging sections with drag-and-drop
Rearranging sections with drag-and-drop

  • To rearrange sections, tap and hold the
    Edit icon
    Move handle and then move your cursor or finger towards your desired
    location. Other sections will move out of the way for where the selected
    section will drop.

Rearranging cards with drag-and-drop
Rearranging sections with drag-and-drop

  • To rearrange cards, tap and hold anywhere on the card and then move your
    cursor or finger towards your desired location.

Don’t you love it when instructions are so short? Simplicity FTW! 🦄

Thanks again Paul,
and Madelena!

Operating script out of your dashboard with consumer enter

ScriptsScripts are parts that permit customers to specify a sequence of actions to be executed by Dwelling Assistant when turned on.

[Learn more]
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, allowing 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 a script on a dashboard.

This allows you to provide the input fields and run the script, unlocking a
whole new dimension of possibilities.

To accompany this new functionality, we’ve created two blueprints to help you
get started with using scripts on your dashboard:

Announce message: This blueprint allows you to create an announce script for
your dashboard pre-configured to a specific media player and text-to-speech
engine. When activated, it will ask the user for the message to play.

Add to to-do checklist: This blueprint permits you to create a script so as to add an
merchandise to a to-do checklist pre-configured to a selected to-do checklist. When activated,
it would ask the consumer for the merchandise so as to add.

New energy graph for individual devices

Digging into your energy data is a very interesting way to find ways to reduce
your household’s energy usage and environmental footprint. 🌱

One of the missing bricks was the ability to see the energy consumption
of individual devices over time. Thanks to
@karwosts, we’ve got a
model new graph on the vitality dashboard that gives this perception!

Utilizing this new graph, now you can simply spot which units are accountable
for which a part of your vitality utilization over time.

Screenshot showing the new energy stacked bar graph of individual devices over time.

For instance, within the above image, it is extremely straightforward to see that the dishwasher
was accountable for the morning spike and the oven for the spike within the night.

New sentences for Help

Assist, our private voice assistant, learned a few tricks this month.

Support for valves has been added. You can now ask Assist to adjust the position
of a valve, or just open or close a valve completely.

Also, cover support has been extended to support the control of the position of
your devices. Currently, most languages only support a single use-case as a
starting point. Setting the position of a single device by targeting its

Set the curtain position to 80%

We are working on extending the use-case coverage to set the position
of multiple devices or complete areas, similar to what is possible with
the open and close sentences.

Screenshot showing a few of the new Assist commands.

The next new trick could be considered a bug fix: Until today it was not
possible to start or stop a vacuum cleaner by voice; Now it can! Assist knows
how to start a vacuum and return it to its base. Here are some example
sentences, in case you have a vacuum cleaner named Dusty:

Start Dusty

Return Dusty to base

The biggest set of changes is for media players. Assist can now pause playback,
resume playback, skip to the next media, and set the volume of media players!

Be aware that currently, these sentences are limited to targeting a single
device by its name, for example:

Skip to the next song on the TV

We are actively working on extending the logic of these new intents to allow
you to target areas and only affect the desired media player(s).

Disabling the remote activation of the Home Assistant Remote UI

If you are using Home Assistant Cloud, you’ll be able to entry
your Dwelling Assistant occasion remotely utilizing the Distant UI characteristic.

Suppose this characteristic is, for some motive, disabled, and you might be at the moment not
at dwelling. In that case, you’ll be able to allow the Distant UI characteristic remotely by
logging into your Nabu Casa account and
request your Dwelling Assistant occasion to show it on.

Suggestions from the neighborhood has proven that this characteristic just isn’t at all times desired,
and this launch provides a brand new choice to disable the distant activation of the
Distant UI characteristic. As soon as disabled, the Distant UI characteristic can solely be enabled
domestically out of your Dwelling Assistant occasion.

Screenshot showing the new advanced option that allows disabling remote activation of the Home Assistant remote UI.

Translating states in your templates

Are you utilizing templatesA template is an automation definition that may embrace variables for the service or knowledge from the set off values. This permits automations to generate dynamic actions.
[Learn more]
to send notifications in automations? If so,
@PiotrMachowski may simply have added one thing new you want!

A brand new template technique, state_translated, to translate entity states immediately
out of your templates! Take into account this template instance:

# Untranslated
 states("binary_sensor.movement_backyard")   # Reveals: on
 states("solar.solar")   # Reveals: below_horizon

The above instance reveals the uncooked state of two entities. Nevertheless, with the
new state_translated technique, you may get the state in a human-readable kind:

# Translated
 state_translated("binary_sensor.movement_backyard")   # Reveals: Detected
 state_translated("solar.solar")   # Reveals: Under horizon

Even higher, it makes use of the default language of your Dwelling Assistant occasion. So,
should you use Dwelling Assistant in a distinct language, the translated state will
be in that language.

Home Assistant boots twice as fast

In case you didn’t know, every release @bdraco improves the efficiency
on some side of Dwelling Assistant. He has been on it for a very long time and retains
pushing to enhance it.

As a matter of truth, it has turn into so common that we don’t at all times spotlight
his monumental efforts towards this objective in our launch notes. Sorry! 🙏

Nevertheless, on this launch, his efforts are so noticeable that we needed to
name it out: Dwelling Assistant now boots on common twice as quick! 🚀

That may be a big enchancment @bdraco!! Thanks in your steady work on
making Dwelling Assistant sooner and sooner! ❤️

Different noteworthy adjustments

There are numerous extra enhancements on this launch; listed here are among the different
noteworthy adjustments this launch:

  • The climate entity now has a toggle service (climate.toggle).
  • Matter lights now assist transitions, good! Thanks, @marcelveldt!
  • We heard you want downloading CSVs! So, we added the flexibility to obtain
    the vitality dashboard knowledge to a CSV file now as effectively! Thanks @karwosts!
  • After suggestions and experiences on the automated Zigbee machine firmware updates
    launched in a earlier launch, this launch brings a stricter and
    extra strong replace system to ZHA. Thanks @dmulcahey & @puddly!
  • The Tessie integration now offers charging and vary sensors.
    Thanks @Bre77!
  • myUplink units can now be up to date immediately from Dwelling Assistant.
    Superior @astrandb!
  • DuneHD media gamers now assist searching media information and taking part in them.
    Thanks @iliessens!
  • The Convey! now brings in a brand new “not too long ago” checklist. Good @miaucl!
  • @lellky added setpoints as quantity entities for followers to the
    Flexit Nordic (BACnet) integration, thanks!
  • The dialog to regulate long-term statistics now has automated outlier detection!
    That may be a very sensible and useful addition. Thanks @karwosts!

New integrations

We welcome the next new integrations on this launch:

This launch additionally has new digital integrations. Digital integrations are stubs
which can be dealt with by different (current) integrations to assist with findability.
The next digital integrations have been added:

Integrations now available to set up from the UI

The following integration us now available via the Home Assistant UI:

Release 2024.3.1 – March 14

Release 2024.3.2 – March 22

Release 2024.3.3 – March 22

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 is an excellent place to be
at, and don’t forget to join our amazing

Discovered a bug or subject? Please report it in our issue tracker,
to get it fastened! Or, test our assist web page for steerage for extra
locations you’ll be able to go.

Are you extra into e mail? Signal-up for our Constructing the Open Dwelling Publication
to get the most recent information about options, issues occurring in our neighborhood and
different information about constructing an Open Dwelling; straight into your inbox.

Backward-incompatible changes

If you’re a customized integration developer and need to study breaking
adjustments and new options accessible in your integration: You should definitely comply with our
developer blog. The next are probably the most notable for this launch:

All adjustments

In fact, there may be much more on this launch. Yow will discover a listing of
all adjustments made right here: Full changelog for Dwelling Assistant Core 2024.3