2024.8: Beautiful badges!
Home Assistant 2024.8! 🎉
Warning! An awesome and huge release is coming your way this month!
11! new integrations and 7! integrations are now available via the UI; We have many noteworthy improvements to integrations and even more noteworthy improvements to Home Assistant itself. And that… is just the tip of the iceberg! 🗻
I’m most excited about the new badges for your dashboard.
I mean, the old ones weren’t the prettiest, but these new ones are definitely
gorgeous! Oh! And if you missed the last dashboard stream, I would highly recommend
watching the recording
This release also marks a significant milestone in the history of Home Assistant, as we are saying goodbye to service calls. Services have been around since day one, but we are now moving to actions, making things much easier to explain to people new to Home Assistant.
Enjoy the release! 🎉
../Frenck
- Dashboards - Chapter 2
- Goodbye service calls, hello actions 👋
- Sort data tables by created or last modified
- Control Home Assistant using AI with Ollama
- Integrations
- Zigbee Home Automation (ZHA) updates
- Matter updates
- KNX can now be managed via the UI
- Other noteworthy changes
- Integrations and helpers set up via YAML, now visible in the UI!
- Patch releases
- Need help? Join the community!
- Backward-incompatible changes
- All changes
Dashboards - Chapter 2
As part of our roadmap, work has continued on making dashboard customization and organization easier and more intuitive.
Last week, we had the “Dashboards Chapter 2”
As part of our continuous improvement, this month we have fully redesigned and revamped the badges for your dashboards!
New badges for your dashboard
We already wrote about it extensively in our Dashboard Chapter 2 blog post and this release introduces our redesigned badges!
This is a big revamp of the original badges that have been in Home Assistant
since, well, forever. The new badges are designed to match the design of the
Mushroom
![New badges sitting on top of a dashboard view!](/images/blog/2024-07-dashboard-chapter-2/new-badges.png)
These new badges match the functionality of the previous design but are now even more feature-rich. Of course, they are fully configurable from the UI, allowing you to tweak them to your needs. You can specify whether the icon, name, and/or state will be visible, and you can configure the contents within each of them.
Everything can, of course, be dragged and dropped in the order you like 😎
Not just that, the new badges also come with visibility options, the same as we have introduced for cards in Home Assistant 2024.6. This means you can show or hide them based on who is viewing the dashboard, what screen size it is displayed within, whether an entity is in a certain state, and more.
![Screenshots; left showing the add badge dialog wich include the custom mushroom template badge, on the right shows the visibility tab and options badges now have.](/images/blog/2024-08/badges-add-visibility.png)
The best news of all? The new badges work across both the new sections view and
the old masonry view! 🎉 Heck!, we even have support for custom badges, like the
custom template one released by the Mushroom
If you have existing old-style badges today, don’t worry! They will be automatically converted to the new badges when you upgrade to this release.
Optimized information density for the Sections view
For this release, we have also fine-tuned the design grid for our experimental Sections view.
The height of each row has been reduced, allowing more information to be displayed on the screen. Hours of pixel pushing have also reduced the gap between the Tile card contents and its features, resulting in a cleaner and more uniform appearance.
The 2024.7 release on the left and this 2024.8 release on the right.
If you have been experimenting with sections and have resized some of your cards, you may need to readjust the sizes to accommodate these changes.
Goodbye service calls, hello actions 👋
This release marks an important milestone in the evolution of Home Assistant: we are saying goodbye to service calls and hello to actions!
If you are a long-time user of Home Assistant reading this now: don’t be alarmed by this change, nothing breaks with this, and everything will continue to work just as it did before.
In the 2024.1 release, we unified the actions in the Home Assistant automationAutomations in Home Assistant allow you to automatically respond to things that happen in and around your home. [Learn more] & script editors. The goal of that change was to make our automation editor easier for newer users to understand by removing the “Service call” layer and terminology.
![Screenshot showing the new add action dialog utilizing the search function to find whatever you need.](/images/blog/2024-01/add-action-search.png)
The above screenshot shows the UI that has been in use since the January release, and was very well received in general. However, the underlying terminology in our documentation and all other places in Home Assistant still used the “service call” terminology.
Additionally, the term “services” in Home Assistant is overloaded and ambiguous. It is used for both the services you can call in Home Assistant and services you might integrate with, like weather or music services. In the latter case, we are talking about integrating with a service provided by a program or website, which is referenced in our Settings page as Devices & services. 😵💫
To make things clearer, we are now changing the terminology around service calls in Home Assistant from “services” to “actions” everywhere.
Every occurrence in the documentation, the UI, the code, and everywhere else in Home Assistant, has been replaced with “action”. Unlike the previous services which were “called”, actions are “performed”.
![Screenshot of the developers tools, which also renamed all occurances of services to actions.](/images/blog/2024-08/actions-developers-tools.png)
If you write automations in YAML, you will notice that the service
key
in your actions is now called action
. For example:
- action: light.turn_on
target:
area: living_room
Existing UI-managed automations will be automatically converted the next time they
are edited and saved. If you write automation in YAML, you can
use either action
or service
, as this change is fully backward compatible,
but we recommend using action
from now on.
Sort data tables by created or last modified
You’ve added a new integration, a new device, or maybe just updated Home Assistant and wondering what new entities or devices you have available?
This release will help you with that. Home Assistant now tracks when entities and devices, and many other things were created or last modified. If these are shown in a table, it means you can now sort them by the date they were created or last modified; helping you find those recently added or modified items.
![Screenshot showing the new created and modified columns of the entities table, allowing one to sort on these new values.](/images/blog/2024-08/data-tables-created-modified-columns-sorting.png)
The created and modified columns are hidden by default, but you can make them
visible by clicking the
You might notice that most entities and devices do not have this created or modified data populated yet. Well this data has only started being recorded in this release, and cannot be applied retroactively, but going forward it should only get more useful.
Control Home Assistant using AI with Ollama
In the 2024.6 release, we introduced the ability to use the OpenAI and GoogleAI integrationsIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] to control your home using Large Language Models (LLMs). Many of you requested this to work with a local hosted LLM as well.
Today we are happy to announce that Home Assistant now supports control via local LLMs too!
This is achieved thanks to @Shulyaka
Allen created a new LLM benchmark suite
Through prompt tuning and fixes included in this release, we have gotten local LLMs to score a reasonable 84%. We will continue to test new models while improving our prompts and tools to achieve a higher score.
Overview of performance of Ollama running different local models ran against the LLM benchmark suite
If you want to experiment with local LLMs using Home Assistant, we currently recommend using the Llama 3.1 8B model and exposing fewer than 25 entities. Note that smaller models are more likely to make mistakes.
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:
-
Autarco, added by @klaasnicolaas
Monitor the performance of your Autarcoconnected solar panels, inverters, and batteries. -
Bryant Evolution, added by @danielsmyers
Control your Bryant EvolutionHVAC system. -
Dio Chacon, added by @cnico
Connect your Dio Chacon devicesvia RF 433 Mhz or Wi-Fi. -
ElevenLabs, added by @sorgfresser
ElevenLabs text-to-speechservice, provides natural sounding voices. -
iotty, added by @pburgio
Control your iotty Smart Homelight switch, gate, smart cover, and outlet devices. -
IronOS, added by @tr4nt0r
Integrate your IronOS-powered soldering iron with Home Assistant over Bluetooth. -
Israel Rail, added by @shaiu
Get real-time departure information from the Israel railways. -
LinkPlay, added by @dukeofphilberg
Control various media players based on the LinkPlayprotocol. -
madVR Envy, added by @iloveicedgreentea
Control your madVR Envyvideo processor for your home theater. -
Simplefin, added by @jeeftor
SimpleFIN is a financial data provider that offers a simple and easy-to-use API for retrieving financial data. -
Tesla Fleet, added by @Bre77
Through the Tesla Fleet API, you can connect and monitor various sensors from Tesla vehicles, PowerWall, Solar panels, or Wall connectors.
This release also has new virtual integrations. Virtual integrations are stubs that are handled by other (existing) integrations to help with findability. These ones are new:
-
Mercury NZ Limited, provided by Opower, added by @SplicedNZ
-
MINI Connected, provided by BMW Connected Drive, added by @rikroe
-
Pinecil, provided by ironOS, added by @tr4nt0r
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 HomeKit Bridge integration now supports the event entities representing
doorbells and motion sensors. Big thanks @bdraco
! - To use the above HomeKit feature, @bdraco
added support for event entities to the UniFi Protect, Doorbird, and August integrations. Awesome! - Talking about event entities, @mib1185
added event entities to the Feedreader integration. So you can now easily automate when a new article shows up in one of the news feeds you follow. Great! - The OpenAI conversation integration now defaults to the, much cheaper,
gpt-4o-mini model. Thanks @allenporter
! - The WLED integration now supports CCT LED strips, thanks to @Suxsem
! -
Tessie received lots of attention from @Bre77
this release, adding tons of new entities and features to the integration. Great job! -
@joostlek
and @andrew-codechimp have been extending the Mealie integration with a lot of new actions and features. Most notably, the ability to import recipes, set meal plans, and view shopping lists. Thanks! - You can now control your Reolink chime with the Reolink integration, thanks
to @starkillerOG
! - The Roborock integration now supports the Roborock Zeo
washer/dryer. Cool @Lash-L ! -
@tr4nt0r
migrated the Habitica Dailies and to-do’s to support our to-do entities. Nice! - Thanks to @tanchu
, the Xiaomi Miio integration now supports Xiaomi air purifiers and humidifiers. Great! -
@bieniu
extended the Shelly integration to support Shelly virtual components . These virtual components can be used to add Home Assistant entities to your Shelly device, such as the Shelly WallDisplay dashboard, or pass Home Assistant sensor data to Shelly scripts . Nice!
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.
-
BMW Connected Drive, done by @rikroe
-
TechnoVE, done by @Moustachauve
-
Tessie, done by @Bre77
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:
-
Bluesound, done by @LouisChrist
-
Genius Hub, done by @GeoffAtHome
-
History stats, done by @gjohansson-ST
-
Mastodon, done by @andrew-codechimp
-
Russound RIO, done by @noahhusby
-
Wake on LAN, done by @gjohansson-ST
-
Worldclock, done by @gjohansson-ST
Farewell to the following
The following integrationsIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] are also no longer available as of this release:
-
UE Smart Radio has been removed; the service has been discontinued
.
Zigbee Home Automation (ZHA) updates
The Zigbee Home Automation (ZHA) got a massive overhaul this release!
What this means for you? Well… basically: nothing! And this sounds odd, but that is a good thing!
The whole integration has been split into a separate codebase, making it easier to maintain and improve. This is a huge step forward for the integration, and took months of work to get done.
You will not notice anything different right now, but this change will make the integration easier to maintain and improve in the future, including allowing code contributors to contribute more easily.
Thanks for the dedication and the huge amounts of hard work on this integration
@dmulcahey
Matter updates
There are a couple of updates for the Matter integration this release, while we are working hard to get the integration ready for official Matter certification.
The Matter integration can now provide update entities. If your Matter device has a firmware update available, Home Assistant will now be able to inform you about it and update the device for you. 🎉
This update feature is available for all Matter devices, where manufacturers provide firmware updates via the official Matter update channels. Not many manufacturers are involved in delivering these updates yet, but this is a great step forward, and we hope many manufacturers using Matter will follow this example.
Event entities provided by the Matter integration have been improved. They will now provide more event types, allowing you to react to things like single press or double press events with ease.
Additionally, @jvmahon
These last two features, are amazing improvements to the Matter integration, but they are mainly a highlight. Many Matter device types have seen improvements, including more (configuration) entities and other improvements.
KNX can now be managed via the UI
The KNX integration introduces the ability to manage entities directly from the UI. 🎉
If you have an ETS project file, configuring your devices is now more intuitive; you can easily select an actuator from the side panel and drag and drop its assigned group addresses into the configuration. Alternatively, addresses can be found by name or number using dropdown menus.
Create, update, and delete KNX switch and light entities directly from the KNX panel without touching any YAML. 😎
More improvements have been made under the hood. One of the most notable changes is the support for a broader range of Data Point Type (DPT) definitions. These can be used directly within actions and triggers and inspected in the KNX GroupMonitor.
Thank you for working so hard on this one @farmio
Other noteworthy changes
There are many more improvements in this release; here are some of the other noteworthy changes this release:
- We are proud of our Open Home Foundation
, so we will now show its pretty logo on the Home Assistant loading and information screens. Thanks @balloob ! -
Timer support using Assist for mobile devices. This means you can now
control timers from your mobile device or tablet. Thanks @balloob
! - You can now ask Assist for the current time and date, thanks @synesthesiam
! -
@synesthesiam
also switched our voice activity detection to microVAD ! Using this we are able to detect the end of a speech command much better in noisy environments, even with music in the background. Cool! - The picture elements card can now be fully managed in the UI using a
brand-new visual editor. Fantastic work there @karwosts
! - Home Assistant will now raise a repair issue if a script can’t be set up
(for example, because of YAML syntax errors). Thanks @emontnemery
! - If Home Assistant finds an integration set up that has been removed
(like when you remove a custom integration), it will now raise a repair issue
to help you clean up anything left behind. Thanks @joostlek
! -
Group now has support for grouping two new entity types. @joostlek
added support for grouping notify entities, and @frenck added support for grouping button entities. Nice! - The Generic Thermostat and Hygrostat helpers will now be linked to the
device that provided the actuator entity, thanks @dougiteixeira
! -
@gjohansson-ST
did the same, he added a link to the History stats helper to the device that provided the sensor entity. - You can now set up button, image, select, and switch templates
entities, straight from the UI. Awesome job @dougiteixeira
! -
@karwosts
added a button to the actions developer tools to copy the action response as JSON for use in templates. Nice! - The picture, picture elements, picture entity, and picture glance cards
can now get their image from the person entity! You don’t need to set a static
image to represent a person, it will now automatically fetch the person’s picture
for you. Thanks @Quentame
!
Integrations and helpers set up via YAML, now visible in the UI!
Most popular integrationsIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] and helpers can be set up directly from the Home Assistant user interface. However, we still have a lot of older or less used integrations that can only be set up using manual YAML configuration. We are working hard to move more and more of these integrations to the UI, however, this takes time and effort.
The problem with these integrations is that they are not visible in the UI when they are set up using YAML. What we often see is that someone sets up an integration using YAML and then cannot see it on the integrations page, often resulting in questions in our community about where to find it.
As of this release, we have drastically improved this situation. All integrations, regardless of how they are set up, are now visible on the integrations page in the UI. This means that even if you set up an integration using YAML, you can now find it in the UI and view its provided entities.
![Screenshot showing the demo integration, which is set up manually via YAML, showing up in the UI on the integrations dashboard.](/images/blog/2024-08/yaml-integration-listed.png)
Integrations originating from manual YAML configuration can be recognized by the
Similarly, we also have many helpers that can be set up using YAML configuration. These sometimes showed up in the UI, but often did not. We have adjusted this as well, and made sure that all helpers are now visible in the UI, regardless of how they are set up.
Things set up manually using YAML are still managed using YAML. This means that if you want to change the configuration of these integrations or helpers, you will need to do so in the YAML configuration files.
Patch releases
We will also release patch releases for Home Assistant 2024.8 in August. These patch releases only contain bug fixes. Our goal is to release a patch every week (around Friday).
2024.8.1 - August 10
- Add support for v3 Coinbase API (@TomBrien
- #116345 ) - Bump OpenWeatherMap to 0.1.1 (@freekode
- #120178 ) - Fix limit and order property for transmission integration (@fustom
- #123305 ) - Fix doorbird with externally added events (@bdraco
- #123313 ) - Bump aiorussound to 2.2.2 (@noahhusby
- #123319 ) - Revert “Fix blocking I/O while validating config schema” (@emontnemery
- #123377 ) - Ensure legacy event foreign key is removed from the states table when a previous rebuild failed (@bdraco
- #123388 ) - Bump aiohttp to 3.10.2 (@bdraco
- #123394 ) - Also migrate dsmr entries for devices with correct serial (@dupondje
- #123407 ) - Add missing logger to Tessie (@Bre77
- #123413 ) - Bump YoLink API to 0.4.7 (@matrixd2
- #123441 ) - Support action YAML syntax in old-style notify groups (@frenck
- #123457 ) - Bump ZHA library to 0.0.29 (@puddly
- #123464 ) - Bump pyjvcprojector to 1.0.12 to fix blocking call (@SteveEasley
- #123473 ) - Bump monzopy to 1.3.2 (@JakeMartin-ICL
- #123480 ) - Fix startup blocked by bluesound integration (@LouisChrist
- #123483 ) - Update frontend to 20240809.0 (@frenck
- #123485 ) - Bump zha lib to 0.0.30 (@dmulcahey
- #123499 ) - Bumb python-homewizard-energy to 6.2.0 (@DCSBL
- #123514 ) - Fix cleanup of old orphan device entries in AVM Fritz!Tools (@mib1185
- #123516 ) - Bump pydaikin to 2.13.2 (@mattyway
- #123519 ) - Bump AirGradient to 0.8.0 (@joostlek
- #123527 ) - Upgrade chacon_dio_api to version 1.2.0 (@cnico
- #123528 )
2024.8.2 - August 16
- Avoid Exception on Glances missing key (@wittypluck
- #114628 ) - Fix Madvr sensor values on startup (@iloveicedgreentea
- #122479 ) - Drop violating rows before adding foreign constraints in DB schema 44 migration (@emontnemery
- #123454 ) - Handle Yamaha ValueError (@pssc
- #123547 ) - Bump aiohttp to 3.10.3 (@bdraco
- #123549 ) - Update knx-frontend to 2024.8.9.225351 (@farmio
- #123557 ) - Fix secondary russound controller discovery failure (@noahhusby
- #123590 ) - Change WoL to be secondary on device info (@gjohansson-ST
- #123591 ) - Ensure HomeKit connection is kept alive for devices that timeout too quickly (@bdraco
- #123601 ) - Bump
aioshelly
to version 11.2.0 (@bieniu- #123602 ) - Bump pydaikin to 2.13.4 (@kingy444
- #123623 ) - System Bridge package updates (@timmo001
- #123657 ) - Bump aiohomekit to 3.2.2 (@bdraco
- #123669 ) - Fix startup block from Swiss public transport (@miaucl
- #123704 ) - Bump pyschlage to 2024.8.0 (@dknowles2
- #123714 ) - Update AEMET-OpenData to v0.5.4 (@Noltari
- #123716 ) - Update aioairzone-cloud to v0.6.2 (@Noltari
- #123719 ) - Update aioqsw to v0.4.1 (@Noltari
- #123721 ) - Bump ZHA lib to 0.0.31 (@dmulcahey
- #123743 ) - Update wled to 0.20.2 (@frenck
- #123746 ) - Fix error message in html5 (@mib1185
- #123749 ) - Bump py-nextbusnext to 2.0.4 (@ViViDboarder
- #123750 ) - Bump python-nest-sdm to 4.0.6 (@allenporter
- #123762 ) - Update xknx to 3.1.0 and fix climate read only mode (@farmio
- #123776 ) - Fix KNX UI Light color temperature DPT (@farmio
- #123778 ) - Fix status update loop in bluesound integration (@LouisChrist
- #123790 ) - Bump py-synologydsm-api to 2.4.5 (@mib1185
- #123815 ) - Fix blocking I/O of SSLContext.load_default_certs in Ecovacs (@edenhaus
- #123856 ) - Fix translation for integration not found repair issue (@mib1185
- #123868 ) - Handle timeouts on Airzone DHCP config flow (@Noltari
- #123869 ) - Bump pylutron_caseta to 0.21.1 (@bdraco
- #123924 ) - Fix PI-Hole update entity when no update available (@mib1185
- #123930 ) - Bump LaCrosse View to 1.0.2, fixes blocking call (@IceBotYT
- #123935 ) - Bump pypck to 0.7.20 (@alengwenus
- #123948 ) - Environment Canada weather format fix (@gwww
- #123960 ) - Bump pyhomeworks to 1.1.1 (@emontnemery
- #123981 ) - Ensure event entities are allowed for linked homekit config via YAML (@bdraco
- #123994 ) - Bump openwebifpy to 4.2.7 (@autinerd
- #123995 ) - Re-enable concord232 (@joostlek
- #124000 ) - Bump aiounifi to v80 (@Kane610
- #124004 ) - Fix rear trunk logic in Tessie (@Bre77
- #124011 ) - Bump bluetooth-adapters to 0.19.4 (@bdraco
- #124018 ) - Fix loading KNX integration actions when not using YAML (@farmio
- #124027 ) - Bump aiomealie to 0.8.1 (@joostlek
- #124047 ) - Exclude aiohappyeyeballs from license check (@joostlek
- #124041 )
2024.8.3 - August 25
- Skip NextBus update if integration is still loading (@drozycki
- #123564 ) - Bump yalexs to 6.5.0 (@bdraco
- #123739 ) - Bump yalexs to 8.0.2 (@bdraco
- #123817 ) - Bump aioshelly to 11.2.4 (@bdraco
- #124080 ) - Add Alt Core300s model to vesync integration (@cdnninja
- #124091 ) - Bump pybravia to 0.3.4 (@Drafteed
- #124113 ) - Bump aiohomekit to 3.2.3 (@bdraco
- #124115 ) - Bump nest to 4.0.7 to increase subscriber deadline (@allenporter
- #124131 ) - Bump tplink-omada-api to 1.4.2 (@MarkGodwin
- #124136 ) - Bump aiohttp to 3.10.4 (@bdraco
- #124137 ) - Update Matter light transition blocklist to include GE Cync Undercabinet Lights (@cjmaio
- #124138 ) - Shelly RPC - do not stop BLE scanner if a sleeping device (@thecode
- #124147 ) - Fix shelly available check when device is not initialized (@bdraco
- #124182 ) - Bump pyhomeworks to 1.1.2 (@emontnemery
- #124199 ) - Bump aiohttp to 3.10.5 (@bdraco
- #124254 ) - Update xknx to 3.1.1 (@farmio
- #124257 ) - Bump python-roborock to 2.6.0 (@allenporter
- #124268 ) - Prevent KeyError when Matter device sends invalid value for StartUpOnOff (@marcelveldt
- #124280 ) - Don’t abort airgradient user flow if flow in progress (@joostlek
- #124300 ) - Bump yalexs to 8.1.2 (@bdraco
- #124303 ) - Bump python-holidays to 0.54 (@gjohansson-ST
- #124170 ) - Bump python-holidays to 0.55 (@gjohansson-ST
- #124314 ) - Add missing strings for riemann options flow (@karwosts
- #124317 ) - Fix Spotify Media Browsing fails for new config entries (@PeteRager
- #124368 ) - update ttn_client - fix crash with SenseCAP devices (@angelnu
- #124370 ) - Add supported features for iZone (@Swamp-Ig
- #124416 ) - Bump yalexs to 8.1.4 (@bdraco
- #124425 ) - Bump aiohue to version 4.7.3 (@idekker
- #124436 ) - Don’t raise WLED user flow unique_id check (@joostlek
- #124481 ) - Bump yalexs to 8.3.3 (@bdraco
- #124492 ) - Bump yalexs to 8.4.0 (@bdraco
- #124520 ) - Bump yalexs to 8.4.1 (@bdraco
- #124553 ) - Fix missing id in Habitica completed todos API response (@tr4nt0r
- #124565 ) - Only support remote activity on Alexa if feature is set and at least one feature is in the activity_list (@jbouwh
- #124567 ) - Revert “Exclude aiohappyeyeballs from license check” (@bdraco
- #124116 )
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
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:
Recorder database upgrade notice
This notice applies only if you use the recorder integration with a MySQL or PostgreSQL database. If you are using the default SQLite database, you can ignore it.
This release includes a database upgrade/migration that increases the size of
the number we can store for the identifier fields. For a more technical
explanation, we are upgrading integer fields for ID columns from a 32-bit
integer to BIGINT
, which is a 64-bit integer.
This can cause the database upgrade to take longer than usual, depending on the size of your database.
Please be patient and let the upgrade process finish. Do not interrupt the upgrade process, as this can lead to a corrupted database.
(@emontnemery
BlinkStick
The Blinksticklight integration is disabled because it requires software that is not open source. Any help or contributions to make this integration work without the closed-source software is welcome.
(@joostlek
Bluesound
Sources behave slightly differently. Radio station providers (like TuneIn and Radio Paradise) are no longer part of the source list and are not selectable as sources.
Presets that play a specific radio station can be created in the BluOS app and are displayed as sources in Home Assistant.
The currently selected source tries to match those presets and falls back to the radio station provider (like TuneIn, Radio Paradise).
(@LouisChrist
BMW Connected Drive
Describing attributes car
and vin
have been removed from BMW entities.
If you need to look them up, please get them from the device info screen.
(@rikroe
Climate
Scenes that use the deprecated auxiliary heat (aux_heat
attribute)
will no longer restore/set the auxiliary heat state when the scene
is activated.
(@bjpetit
Concord232
The Concord232 integration is disabled because it requires software that is not open source. Any help or contributions to make this integration work without the closed-source software is welcomed.
(@joostlek
DoorBird
Previously, resetting the device favorites required working out a complicated URL. A button is now available to perform this operation.
(@bdraco
Dovado
The Dovado integration is disabled because it requires software that is not open source. Any help or contributions to make this integration work without the closed-source software is welcomed.
(@joostlek
Ecovacs
The attributes on the vacuum entity for the lifespan of the main brush, side brush, and filter are deprecated and will be removed in 2025.2.
These attributes are superseded by dedicated sensor entities.
(@mib1185
HomeKit Bridge
PM2.5 air quality sensors are now mapped to the US EPA AQI scale
(@sarabveer
Lights
The following attributes are no longer saved in the database for light entities because their combinations would quickly fill up the database, and they are never used by Home Assistant:
brightness
color_mode
color_temp
color_temp_kelvin
effect
hs_color
rgb_color
rgbw_color
rgbww_color
xy_color
This change will not impact the operation of your lights, but it will reduce the amount of data stored in the database.
(@bdraco
Matter
Multi-press events are now split into their own dedicated event type, such as
multi_press_1
, multi_press_2
, etc., making it easier to automate multiple
presses instead of looking manually at the number of presses count.
If you have used the current event type in your automations, you will need to update them to use the new event types.
(@marcelveldt
MQTT
The schema
option has been removed from the MQTT vacuum schema. YAML configs
still containing this option will break after 6 months of deprecation. Users
have been warned with a repair. Discovery configs will not break if the schema
options are still in the config, but they will be ignored, and an error message
will be logged to notice.
(@jbouwh
MVG
(@joostlek
The MVG integration is disabled because it requires software that is not open source. Any help or contributions to make this integration work without the closed-source software is welcome.
National Weather Service (NWS)
NWS weather entities no longer have a detailed_description
in the return
from the weather.get_forecasts
service.
A new service, nws.get_forecasts_extra
, is provided that includes
detailed_description
. The detailed_description
is no longer provided
for hourly
forecasts in the nws.get_forecasts_extra
service as the API
does not return data. However a short_description
is now available.
NextBus
The messages
, directions
, and attribution
attributes have been removed from
the sensor. The new API doesn’t provide these anymore.
OpenAI Conversation
The previously deprecated 256
, 512
, and 1024
values for the size argument
for the generate_image
action have been removed. They have already been
unsupported in the past (replaced with 1024x1024
by default).
If you still use these values in your automations or scripts, you will need to update them to use “1024x1024”, “1024x1792”, or “1792x1024” values.
(@Shulyaka
WLED
The WLED integration now requires a WLED device running at least
WLED 0.14.0
(@frenck
Xiaomi Miio
The Nature
and Normal
preset modes will be renamed to nature
and normal
to support translations.
If you have automations or scripts that use the Nature
or Normal
preset
modes, you will need to update them to use nature
and normal
instead.
(@piitaya
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:
- Climate entity now validates temperature provided in action calls
- model_id added to DeviceInfo
- New entity feature flags in FanEntity
- New HVACAction DEFROSTING
- Services are now actions
- Set up your DataUpdateCoordinator with a setup method
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.8