2024.9: Sections go BIG – Residence Assistant

Residence Assistant 2024.9! šŸŽ‰

Many neighborhood members based mostly within the northern hemisphere have taken benefit of the nicer climate to take a while off. Residence Assistant releases have continued to develop for a while, and this one may not be as gargantuan in dimension as earlier releases, however it nonetheless packs some actually cool options and bulletins.

This launch consists of larger sections, smarter vitality monitoring, and a brand new LLM possibility. Weā€™ve added five new integrations, together with one present integration being added to the UI. On high of all that, weā€™ve introduced a brand new Works with Residence Assistant accomplice, and the end result of a mission to make sure our mission is actually open supply.

We hope youā€™ve been capable of get pleasure from a while in, and away, out of your good dwelling this month as properly.

Benefit from the launch!

Sections go BIG

Within the drive to provide our customers extra customization and group choices for his or her dashboards, weā€™ve added some new choices to our Sections view that basically lets us take massive benefit of resizable cards. These powerful customization features can affect the predictability of where cards or sections will go, especially when switching between desktop and mobile views, and we have found it works best with large cards. As always, the choice of how to use it is up to you.

Screenshot showing sections that are all 1 section wide, on the right showing a section that is 2 sections wide.
Screenshots showing a section that is 2 sections wide.

Wider sections

Sections can be expanded to span multiple sections. Now you can, for example, have your security camera feed span two sections or have a massive three-section wide map.

Cards and sections will continue to follow the Z-Grid rules, which can lead to blank spaces if the new wider sections donā€™t fit on a specific part of the screen. If you donā€™t like those blank spaces between sections, you can choose a dense layout. A dense section layout option will attempt to follow the Z-Grid rules, but will fill blank spaces whenever possible. This can affect the order and predictability of your sections, but will maximize screen real estate.

When switching to smaller screens, these larger sections will revert to one section wide (if this causes issues for certain big cards, we would recommend using our device visibility settings).

Screenshot of the section settings

Full span cards

Larger sections mean larger cards. Instead of just stretching out the layout of a card, there is also a new option on cards to have them always use the full width of the section.

Badges

Talking about dashboards, the newly styled badges we introduced in last release, are now more configurable.

Instead of using display mode, you can decide for yourself what element you want to show. This allows you, for example, to hide the icon of an badge and only show the state of the device you want to show in your badge.

Tracking your untracked energy

In April, we introduced a new energy graph for individual devices in our energy dashboard. This allows you to aggregate all your energy monitoring into one graph, giving you a quick way to see your houseā€™s biggest energy-using devices. Big thanks to @karwosts, the unique creator of this graph, who has now up to date it.

Screenshot of the individual device energy graph

We willā€™t all have vitality monitoring for each machine, and in case you have whole-home vitality monitoring (like a wise meter or one thing extra DIY) the up to date graph will calculate the distinction and present your houseā€™s untracked utilization. So hop onto your energy dashboard and begin to sort out your phantom vitality load.

LLM agent choices develop

Once we added the flexibility to make use of Large Language Models (LLMs) in our Voice Assistant, it began with a limited number of conversation agents. These included the cloud-based OpenAI and Google AI integrations, along with the locally-run Ollama integration. All three can now control the devices in your home.

@Shulyaka has now added one other cloud possibility with Anthropic – thanks once more for giving us another choice for experimenting with AI in Residence Assistant. Setting it up generally is a little totally different than different dialog brokers, so check out the documentation.

Now we have up to date our LLM leaderboard to incorporate Anthropic. Each Claude 3 Haiku and Claude 3 Sonnet rating very excessive on our benchmarks and now rank among the many high. Primarily based on the outcomes of the benchmark, now we have set the cheaper Claude 3 Haiku because the default mannequin for the Anthropic integration.

@allenporter added the flexibility to configure the context window dimension of the Ollama integration. The default dimension was elevated, making it carry out 20% higher!

Aqara joins Works with Residence Assistant

Aqara joins Works with Residence Assistant

We recently announced that four Aqara devices are joining our Works with Home Assistant program. Whatā€™s actually thrilling is that these are all Matter gadgets, and Aqara would be the first accomplice to make use of our ā€œWorks through Matter with Residence Assistantā€ badge, giving some nice choices to make use of with Residence Assistantā€™s wonderful Matter integration.

Whatā€™s extra, this would be the first accomplice to hitch since our current replace to this system, that means device-by-device certification that we examined ourselves. This makes it very easy to see what provides you with the very best expertise in Residence Assistant.

Open supply compliance

We have put a lot of work into making sure that Home Assistant is truly open source, from top to bottom. This means ensuring that every library our integrations rely on uses the compliant license. Weā€™re now at more than 2,800 integrations, so as you can imagine, this was not a small task. Working with code owners and library developers, we have painstakingly checked that every library is now using an OSI-approved license.

This would possibly appear to be a small procedural factor, however it’s vital to maintain integrations and Residence Assistant useful far into the longer term. For those whoā€™re not conscious, libraries are what many machine and repair integrations depend on to operate, by calling in extra protocol particular code that purposely sits exterior of the Residence Assistant mission. If a person or company can now not keep libraries, a correct open supply license permits it to be picked up and continued by others.

Integrations

Due to our neighborhood for conserving tempo with the brand new integrationsIntegrations join and combine Residence Assistant together with your gadgets, companies, and extra. [Learn more]
and improvements to existing ones! Youā€™re all awesome šŸ„°

New integrations

We welcome the following new integrations in this release:

This release also has a new virtual integration. Virtual integrations
are stubs that are handled by other (existing) integrations to help with
discoverability. These ones are new:

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:

Now out there to arrange from the UI

Whereas most integrationsIntegrations join and combine Residence Assistant together with your gadgets, companies, and extra. [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.

You can now add a number template helper from the UI Thanks @dougiteixeira!

Farewell to the next

The next integrationsIntegrations join and combine Residence Assistant together with your gadgets, companies, and extra. [Learn more] are also no longer available as
of this release:

  • Asterisk Call Detail Records and Asterisk Voicemail. Previously
    deprecated and now removed. They have been using a deprecated mailbox feature
    that is no longer available.

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.

Discovered a bug or subject? Please report it in our issue tracker,
to get it mounted! Or, verify our assist web page for steering for extra
locations you may go.

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

Backward-incompatible modifications

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:

Asterisk Name Element Data

Asterisk Name Element Data has been deprecated in 2024.3.0 and has now been eliminated.

It was utilizing a deprecated mailbox characteristic that’s now not out there.

(@joostlek#123180)

Asterisk Voicemail

Asterisk Voicemail has been deprecated in 2024.3.0 and has now been eliminated.

It was utilizing a deprecated mailbox characteristic that’s now not out there.

(@joostlek#123180)

Ecovacs

The YAML configuration for the Ecovacs integration was eliminated. The configuration has been moved to the UI in Residence Assistant 2024.2.

The YAML configuration was mechanically imported and ought to be eliminated out of your YAML configuration.

@gjohansson-ST#123605 (documentation)

GPSD

The YAML configuration for the GPSD integration was eliminated. The configuration has been moved to the UI in Residence Assistant 2024.2.

The YAML configuration was mechanically imported and ought to be eliminated out of your YAML configuration.

(@gjohansson-ST#123725) (documentation)

KNX

The KNX Local weather preset modes are renamed to match the KNX specs.

KNX specs Earlier Now
Auto none auto
Consolation consolation consolation
Standby away standby
Economic system sleep financial system
Constructing safety eco building_protection

@farmio#123964 (documentation)

Logi circle

Logitech stopped accepting functions for entry to the Logi Circle API in Could 2022, and the Logi Circle integration has now been eliminated.

@gjohansson-ST#123727

Lupusec

The YAML configuration for the Lupusec integration was eliminated. The configuration has been moved to the UI in Residence Assistant 2024.2.

The YAML configuration was mechanically imported and ought to be eliminated out of your YAML configuration.

@gjohansson-ST#123606 (documentation)

Lutron

In Residence Assistant 2024.2, followers the place transformed from a light-weight entity to a fan entity.
The outdated gentle entities will now not work on this launch and might be eliminated.

@gjohansson-ST#123607 (documentation)

MQTT

The schema possibility was faraway from the MQTT vacuum schema in Residence Assistant 2024.2. It is best to take away this out of your YAML configuration if set.

Handbook configured MQTT vacuum entities will break if the schema possibility continues to be configured.
When utilizing MQTT discovery the choice shall be silently ignored.

@jbouwh#124722 (documentation)

Overkiz

Atlantic CozyTouch Water Heaters will now present the Handbook operation mode as Electrical.

A binary sensor was added to point if the handbook mode is activated.

Customers which have automations or scripts utilizing these entities along with the Handbook mode ought to replace the automations or scripts accordingly.

@ALERTua#124619 (documentation)

Sensibo

The earlier PM2.5 sensor for Pure gadgets was incorrectly reporting a PM2.5 worth, however itā€™s truly a quantity representing an AQI stage. The sensor will now present the brand new states of ā€˜goodā€™, ā€˜averageā€™, and ā€˜dangerousā€™.

@gjohansson-ST#124151 (documentation)

Starline

The horn change has been deprecated since 2024.1 and is now eliminated.

As a substitute of a change a horn button entity was added. Please replace your automations accordingly.

(@gjohansson-ST#123608) (documentation)

System monitor

Removes the deprecated course of sensor from the System Monitor integration.
This sensor has been supplied as a binary sensor for six months, elevating a restore subject.

@gjohansson-ST#123616 (documentation)

TP-Hyperlink Good Residence

The binary sensor for ā€œReplace out thereā€ will now not be supplied by the TP-Hyperlink Good Residence integration.

It will likely be changed in a subsequent launch with the Replace entity however is disabled for now as a result of stability points when calling the TP-Hyperlink cloud API to verify the newest firmware model. This may occasionally trigger gadgets to go offline. They should be power-cycled to operate once more. The sensor was additionally unreliable and will have returned incorrect information due to price limiting from the TP-Hyperlink cloud.

@sdb9696#124930 (documentation)

Velux

The YAML configuration for the Velux integration was eliminated. The configuration has been moved to the UI in Residence Assistant 2024.2.

The YAML configuration was mechanically imported and ought to be eliminated out of your YAML configuration.

@gjohansson-ST#123724 (documentation)

Zigbee Residence Automation

  • The IKEA Starkvind fan modes have been up to date. Automations that used to set the fan to 10% velocity to modify it to ā€œauto modeā€, ought to now be up to date to set the preset to ā€œauto.ā€
    In auto mode, the precise fan velocity is now correctly displayed.

    For extra info, see the PR in the ZHA repo.

  • The firmware replace entity logic has modified. A tool will solely be thought-about ā€œup-to-dateā€ if there’s a recognized firmware replace for it and the present firmware model is bigger than the firmware replace model. If there isn’t any recognized firmware replace, the machine firmware state shall be thought-about ā€œunknownā€, as we are able toā€™t inform if itā€™s updated or not.
    Beforehand, we confirmed ā€œup-to-dateā€ if there was no recognized firmware which misrepresented the state for a lot of gadgets.

@puddly#124804 (documentation)

If you’re a customized integration developer and need to study modifications and
new options out there on your integration: Remember to comply with our
developer blog. The next are essentially the most notable for this launch:

All modifications

After all, there’s much more on this launch. You will discover an inventory of
all modifications made right here: Full changelog for Residence Assistant Core 2024.9