2024.7: Time to resize your cards!

Home Assistant 2024.7! 🎉
Get ready for a really nice release with something interesting for everyone! 🤗
And not just that, I bring you these release notes from our refreshed website 🤩
that Madelena and yours truly have been spontaneously working on over the
past few days. We hope you like it! ❤️
Some fantastic additions to Assist: Timers!
and the ability to expose your scripts to LLMs. In case you missed it,
it has been covered and demonstrated live in our recent
Voice – Chapter 7 livestream!
which you definitely should watch. 📺
The sections view becomes more feature-rich with
every release, and this time, the ability to resize cards
is added. Absolutely the highlight of the release for me!
My second favorite highlight for this release is the ability to
take control of blueprint-based automations.
There are so many amazing blueprints out there,
and many are perfect, but sometimes they fit 90% of what you need. Being able
to take control of that last 10% is just amazing!
Enjoy the release!
../Frenck

Don’t forget to join our release party live stream on YouTube
3 July 2024, at 20:00 GMT / 12:00 PST / 21:00 CEST!

Resize the cards on your dashboard

As part of our roadmap, we’re
continuing to make dashboard organization and customization easier and more
intuitive. This month, we add the ability to resize the cards on your
dashboard!

Resizing is done with a very nice slider interface, found in the card editing
menu under the new Layout tab, where you can preview your changes. Make
small 1×1 buttons or give a map the space it needs. This is only available on
our experimental sections view, which was recently released with drag-and-drop.

It works with every card, which gives users a lot of freedom. Most cards have
been given a built-in minimum and maximum size, to make it easier to get your
layouts just right. If you mess up the look of a card, luckily we have included
a revert button in the
top left corner 😉.
Data tables improvements

Like the last release and release before that, we keep improving our data
tables. We use data tables to organize information in our settings pages,
including our devices and automations pages.
With this release, we add the final big piece of the puzzle: The ability to
customize the columns shown! 😎

By selecting the cog in
the top right, you can not only customize the columns shown by toggling
visibility , but you
can also change the order of the columns by
dragging them around.
Making it even easier to show the data you want, in the order you want it.
Your customized columns and view are stored in your browser, so you only have
to set them up once. They will be remembered the next time you visit the page.
Voice & Assist

This month, we’re thrilled to bring more enhancements to Assist’s out-of-the-box
capabilities. We’ve added support for timers ⏲️ — our third most requested
feature for voice control — and the powerful ability to expose your
scriptsScripts are components that allow users to specify a sequence of actions to be executed by Home Assistant when turned on.
[Learn more] to LLMs (like ChatGPT and Google Gemini) as well! 💪
If you missed it, be sure to check out our recent Voice – Chapter 7 livestream
from June 26th, where we showcased all these exciting developments. You can
read more in our blog post here and watch the full livestream on YouTube. 🎙️
Timers are here!

You asked, and we listened! As of this release, timers are available. This
feature allows you to create, cancel, pause, resume, and adjust timers using
your voice, making everyday tasks like cooking much easier. And yes, you can
set multiple timers at once! 🎉
Read more about timers in the Chapter 7 blog post.
Timers running on an S3 Box, with countdown text and a loading bar!

Note

Timers are available today on ESPHome and Wyoming voice satellites.
To take advantage of this new feature, update these devices to the latest
version.

Expand an LLM using your scripts

You can now expand LLM capabilities by allowing them access to (your choice)
of your scriptsScripts are components that allow users to specify a sequence of actions to be executed by Home Assistant when turned on.
[Learn more]. This feature lets you precisely control what the
LLM does in specific situations, while still benefiting from the flexibility
and natural language processing that AIs excel at.
For example, you can create a “leaving home” script that performs the actions
you want and expose it to Assist. This ensures that commands like
“I’m heading out for a couple of minutes” will run your predefined script,
such as locking the door without turning off the air conditioning.
Read more about expanding LLMs with script in the Chapter 7 blog post.
Take control of blueprint-based automations

BlueprintsA blueprint is a script or automation configuration with certain parts marked as configurable. This allows users to create multiple scripts or automations based on the same blueprint, with each having its own configuration-specific settings.[Learn more] are amazing; they allow you to use automationsAutomations in Home Assistant allow you to automatically respond to things that happen in and around your home.[Learn more]
and scriptsScripts are components that allow users to specify a sequence of actions to be executed by Home Assistant when turned on.
[Learn more] created and shared by other awesome Home Assistant users.
Most are easy to use and set up, but what if that great blueprint you’ve been
using just needs a little tweak? Just that tiny change to make it perfect for
your home?
Well, now you can! 🎉

You can now take full control over the automations created from a blueprint.
By taking control ,
Home Assistant will convert the blueprint automation into a regular,
stand-alone, automation. This allows you to make any tweak you want,
without having to re-invent the wheel.

The cool thing is that it shows you a preview of how the converted automation
would look like before you take over. This way, you can see what you are getting
into before you actually do it.

Integrations

Thanks to our community for keeping pace with the new integrationsIntegrations connect and integrate Home Assistant with your devices, services, and more.
[Learn more]
and improvements to existing ones! You’re all awesome 🥰
New integrations

We welcome the following new integrations in this release:

Aquacell, added by @Jordi1990Monitor your AquaCell water-softener from Home Assistant.

ista EcoTrend, added by @tr4nt0rThe ista EcoTrend integration allows you to import your monthly heating,
hot water, and water consumption and costs from the ista EcoTrend service.

Mealie, added by @joostlekMealie is a self-hosted recipe manager and meal planner. This integration
will pull in your meal plan as calendars in Home Assistant.

Knocki, added by @joostlekKnocki is a smart device that turns any surface into a
remote control, which you can now use in Home Assistant to trigger
automationsAutomations in Home Assistant allow you to automatically respond to things that happen in and around your home.[Learn more].

Noteworthy improvements to existing integrations

It is not just new integrationsIntegrations connect and integrate Home Assistant with your devices, services, and more.
[Learn more] that have been added; existing
integrations are also being constantly improved. Here are some of the noteworthy
changes to existing integrations:

The Matter integration now provides number entities that allow you to
configure the behavior of your Matter lights, thanks @jvmahon!
The TP-Link Smart Home integration has been fully modernized by
@rytilahti, @sdb9696, and @bdraco! It adds support for many new devices
(like hubs) and unlocks many new features in Home Assistant, including
light effects and presets, firmware updates, and so much more!

@tronikos has added support for integrating the camera from the tablet
running Fully Kiosk Browser. Furthermore, there’s now an image entity
for taking screenshots, the ability to send notifications and text-to-speech
messages to the tablet, and the media player can now play videos! Nice!
The Android TV Remote integration now supports browsing your apps
directly from the media browser, thanks @tronikos!
We’ve seen a lot of improvements to the UniFi Protect integration,
thanks to @bdraco. @wfltaylor chipped in as well, adding support for
animal detection sensors. 🐶🐱🐰
The Android Debug Bridge integration now supports remote entities,
allowing you to remotely control your Android TV. Thanks @ollo69!
The Reolink integration has seen a lot of improvements, thanks to
@starkillerOG. Added support for manual recording, software updates
for more cameras, playback of the auto track lens, and support for
their battery-powered cameras through the Reolink Home Hub. 🎥
The Bang & Olufsen integration now supports announcements, and support
for Tidal has been added too! Nice work @mj23000!

@joostlek added the event entity to the Nanoleaf integration, allowing
you to trigger automations when you touch your Nanoleaf panels. Nice!
If you have a Roborock Dyad vacuum, you are in luck as they are now
supported by the Roborock integration. Awesome @Lash-L!
The SwitchBot integration added support for the SwitchBot Lock Pro.
Good work @szclsya!

Integrations reaching platinum quality level

The following integrationsIntegrations connect and integrate Home Assistant with your devices, services, and more.
[Learn more] have reached the platinum 🏆 level on our
integration quality scale. These integrations are
the best of the best and give you an excellent out-of-the-box experience.

Congratulations to all the developers who worked on these integrations!
Now available to set up from the UI

While most integrationsIntegrations connect and integrate Home Assistant with your devices, services, and more.
[Learn more] can be set up directly from the Home Assistant
user interface, some were only available using YAML configuration. We keep moving
more integrations to the UI, making them more accessible for everyone
to set up and use.
The following integrations are now available via the Home Assistant UI:

Farewell to the following

The following integrationsIntegrations connect and integrate Home Assistant with your devices, services, and more.
[Learn more] are no longer available as
of this release:

Aladdin Connect has been removed, as Home Assistant cannot use the
upstream library at this time.

Unify Circuit was deprecated in Home Assistant 2024.5 and has now been
removed.

ESPHome update entities for ready-made projects

Our sister project, ESPHome received a brand new logo this month! 🎉

Looks familiar, right? 😃 That is because ESPHome has been donated to the
Open Home Foundation by Nabu Casa. The same foundation that the Home
Assistant project is part of.
Besides the new logo, ESPHome has added a new feature that works with this
release of Home Assistant: The ability for makers of
ready-made devices or projects running on ESPHome, to provide updates
for their devices directly to Home Assistant.
This means that if you have a device that is powered-by or Made for ESPHome,
and the maker of that device provides updates for it, you can now update that
device directly from Home Assistant; without the need for you to build, adopt,
or set up the ESPHome software yourself! 😎
These two new features—updating from Home Assistant, and the ESPHome
integration reaching the platinum quality level 🏆—make it easier for new
users and creators to use this powerful platform to build a more Open Home.
Other noteworthy changes

There are many more improvements in this release; here are some of the other
noteworthy changes this release:

Link your template entity to an existing device

Template entities are an advanced and powerful way to create your own
entitiesAn entity represents a sensor, actor, or function in Home Assistant. Entities are used to monitor physical properties or to control other entities. An entity is usually part of a device or a service.
[Learn more] in Home Assistant based on any calculation or logic you
can imagine.
One of the most requested features for templateA template is an automation definition that can include variables for the service or data from the trigger values. This allows automations to generate dynamic actions.[Learn more] entities is the
ability to assign and link them to an existing deviceA device is a model representing a physical or logical unit that contains entities.
. Thanks
to @dougiteixeira, you can now do just that! 🎉

Assigning a template entity to an existing device can be very useful if you have
a template that calculates an additional sensor value for a device. For example,
in the screenshot above, a template helper calculates the sum of two sensors
and is linked to the device that has those sensors.

Note

This feature is only available for template entities that are created
from the UI.

Change the radius of your home zone

ZonesZones are areas that can be used for presence detection.[Learn more] in Home Assistant are a great way to define locations on your
map, such as your work, and trigger automations based on your location. The most
powerful zone is undoubtedly the home zone, which you can use to determine
if someone is home, coming home, or leaving.
Until now, the radius of the home zone was fixed at 100 meters, which was not
always ideal for everyone. Although it could be changed using YAML, as of this
release, you can now change the radius of your home zone directly from the
Home Assistant user interface!

Important

If you have currently configured and overridden your home zone using YAML
configuration, this new feature will not be available to you. You can remove
the YAML configuration and restart Home Assistant to enable UI control.

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 forums.
Found a bug or issue? Please report it in our issue tracker,
to get it fixed! Or, check our help page for guidance for more
places you can go.
Are you more into email? Sign-up for our Building the Open Home 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

We do our best to avoid making changes to existing functionality that might
unexpectedly impact your Home Assistant installation. Unfortunately, sometimes,
it is inevitable.
We always make sure to document these changes to make the transition as easy as
possible for you. This release has the following backward-incompatible changes:

Authentication

The legacy API password (legacy_api_password) authentication provider that
was deprecated in Home Assistant 2023.12, has been removed.
(@edenhaus – #119976) (documentation)

Azure DevOps

All attributes of the “latest build” sensor are now deprecated; each now has
a dedicated sensor entity available. If you use these attributes in your
automations or scripts, you need to adjust these to use one of the
new sensors instead.
(@timmo001 – #114948) (documentation)

BMW Connected Drive

The charging mode and charging status sensors have been updated to use lowercase
state values. If you use these sensors in your automations or scripts,
you must update them to use the new lowercase values.
(@rikroe – #118751) (documentation)

Calendar

Calendar service list_events was deprecated in favor of get_events in
Home Assistant 2023.12 and has now been removed.
Use the new get_events service to retrieve events from calendar entities
instead.
(@gjohansson-ST – #118663) (documentation)

ComEd Hourly Pricing

The unit of measurement for the ComEd Hourly Pricing integration has been
corrected from c to ¢/kWh.
(@themaxgross – #115594) (documentation)

DNS IP

The attribute names Resolver and Querytype have been renamed to
resolver and querytype. If you use these in any automations or scripts,
you need to update them to use the new lowercase names.
(@gjohansson-ST – #119727) (documentation)

The attributes resolver, querytype, and ip_addresses for the DNS IP
sensor are excluded from the recorder and no longer stored in history.
(@gjohansson-ST – #119726) (documentation)

Intergas InComfort/Intouch Lan2RF gateway

Based on the boiler display code or fault code, the boiler status
has been refactored to be signified and unique so we can start supporting
localization.
Depending on the old status texts, automations or scripts might break.
You need to ensure your automations and scripts are updated to use the new
status values.
The new display codes are:

0: opentherm

15: boiler_ext

24: frost

37: central_heating_rf

51: tapwater_int

85: sensortest

102: central_heating

126: standby

153: postrun_boiler

170: service

204: tapwater

231: postrun_ch

240: boiler_int

255: buffer

The new fault codes are:

0: sensor_fault_after_self_check

1: cv_temperature_too_high

2: s1_and_s2_interchanged

4: no_flame_signal

5: poor_flame_signal

6: flame_detection_fault

8: incorrect_fan_speed

10: sensor_fault_s1

11: sensor_fault_s1

12: sensor_fault_s1

13: sensor_fault_s1

14: sensor_fault_s1

20: sensor_fault_s2

21: sensor_fault_s2

22: sensor_fault_s2

23: sensor_fault_s2

24: sensor_fault_s2

27: shortcut_outside_sensor_temperature

29: gas_valve_relay_faulty

30: gas_valve_relay_faulty

(@jbouwh – #119207) (documentation)

La Marzocco

On March 19th, 2024, La Marzocco released a machine firmware update, v3.5-rc5,
together with a new version of the La Marzocco Home App.
Once the app update is installed, the previous scheduling functionality is
removed from the app, and a new scheduling mode is shown. This mode is disabled
until the machine’s firmware has also been updated.
Similarly, if the machine’s firmware is updated before the app, the previous
scheduling functionality does not work.
The previous calendar and auto on/off switches are replaced with calendars
and switches per schedule.
(@zweckj – #113935) (documentation)

Logitech Harmony Hub

The harmony switch entities that were deprecated since Home Assistant 2024.1,
have now been removed.
(@joostlek – #119206) (documentation)

OpenWeatherMap

The now obsolete forecast sensors have been removed. They have been
fully replaced by weather.get_forecasts service.
(@freekode – #119922) (documentation)

Shelly

The switch entity for controlling a Shelly Gas Valve Add-on has been removed,
and a valve entity has taken its place. If you use the switch entity
in your automations or scripts, you must update them to use the new
valve entity.
(@bieniu – #119817) (documentation)

SimpliSafe

SimpliSafe no longer contains functionality to set a code for use within Home
Assistant. This was a virtual code that was not used by the SimpliSafe system.
(@bachya – #118759) (documentation)

SQL

An SQL query generating several columns output was putting the additional
attributes on the SQL sensor.
From now on, these are still shown as state attributes but are no longer
recorded in the database as attributes on this particular sensor
(as the data for these attributes are already present in the database
from where they come).
(@gjohansson-ST – #120170) (documentation)

Sun WEG

The new API version this integration now uses doesn’t provide the kWh per kWP
information, so that sensor is no longer available.
(@rokam – #118435) (documentation)

Swiss public transport

Swiss public transport no longer provides additional state attributes; since
the release of Home Assistant 2023.12, all information has been moved to
dedicated individual sensors.
(@miaucl – #120256) (documentation)

Tami4 Edge / Edge+

Due to upstream API changes, the UV & filter’s last replaced date has been
removed.
Additionally, uv_status & filter_status sensor entities have been changed
to uv_installed and filter_installed.
(@Guy293 – #119158) (documentation)

UniFi Protect

The set default doorbell text service (set_default_doorbell_text) has been
removed. UI has removed this functionality in UI Protect 4.x.
It is still possible to set a custom message using the other services
(unifiprotect.add_doorbell_text and unifiprotect.remove_doorbell_text,
and setting it via the select entity), but there is no longer a default.
(@bdraco – #119695) (documentation)

Utility Meter

The source entity, period, and CRON pattern entity state attributes have been
removed from the sensor entity and moved to the integration diagnostics.
Note that these values are constant throughout the lifetime of a utility meter.
(@dgomes – #118637) (documentation)

Weather

Weather service get_forecast was deprecated in favor of get_forecasts in
Home Assistant 2023.12 and has now been removed.
Use the new get_forecasts service to retrieve forecast information
from weather entities instead.
(@gjohansson-ST – #118664) (documentation)

WLED

The previously deprecated firmware binary sensor has been removed.
Use the provided update entity for your WLED device instead.
(@frenck – #119984) (documentation)

Z-Wave

With this release, you will need to update your zwave-js-server instance.
You must use zwave-js-server 1.36.0 or greater (schema 36).

If you use the Z-Wave JS add-on, you need at least version 0.6.0.
If you use the Z-Wave JS UI add-on, you need at least version 3.8.2.
If you use the Z-Wave JS UI Docker container, you need at least version 9.14.2.
If you run your own Docker container or some other installation method, you will need to update your zwave-js-server instance to at least 1.36.0.

(@raman325) (documentation)

If you are a custom integration developer and want to learn about changes and
new features available for your integration: Be sure to follow our
developer blog. The following are the most notable for this release:

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.7

Source link