House Assistant Core 2024.2! 🥰
Undoubtedly, you’ve heard about final yr’s “The Year of the Voice”.
2023 is perhaps over, however we’re positively not performed with voice but! This launch
accommodates some very cool new options for voice.
Not simply that, we’ve additionally launched a voice assistant contest
that you could possibly be a part of, and I’m comfortable to tell you that we’ll have one other voice-related
dwell stream on 21 February 2024, at 12:00 PST / 21:00 CET: Chapter 6!
However there may be extra on this launch moreover voice! There’s drag ’n drop magic for
our automation editor, and now you can replace Zigbee gadgets immediately
from House Assistant. We even have icons in additional locations 🤩, and numerous
new functionalities for Matter gadgets.
Typically, contributions to our open-source undertaking have been wonderful this
month. I’ve by no means seen so many contributed bug fixes, enhancements, and new
options in a single launch. Like… 21 new integrations! That is,
unquestionably, the most important launch we’ve ever put out.
An enormous shout-out to everybody who helped! ❤️
Benefit from the launch!
../Frenck
Oh! And don’t neglect Valentine’s Day is arising! 😘
Don’t neglect to join our release party live stream on YouTube
7 February 2024, at 12:00 PST / 21:00 CET!
Better drag & drop support for automations
Let’s start with some old-fashioned drag ’n drop magic! 🪄
As of this release, dragging and dropping triggers, conditions, and actions in
the automation editor are always enabled. Previously, you had to explicitly
enable re-ordering in the automation editor settings, but now, it is just
always active.
But even more exciting is that you can now drag and drop elements into other
nested elements! For example, you can now drag a condition into
the condition of an if-then or choose action. 🤯
Export data from the history dashboard
The following feature might be small, but it is a big deal for many. Home
Assistant stores your data privately and locally; it is your data. To make
this data more accessible, we’ve added a new feature to the history dashboard.
You can now download the data you are viewing in the history dashboard. This
allows you to further analyze the data in, for example, Excel or to visualize
it in other ways.
The button will export and download the data you currently view in the history
dashboard as a CSV file.
Thanks for this one @balloob!
Improved error responses when using Assist
If you use Assist, our non-public voice assistant, you might have
seen that its responses weren’t significant when one thing was not understood.
Among the errors encountered whereas utilizing Help can simply be fastened in your
facet by including aliases to entities or areas, exposing entities to Help,
or assigning entities and gadgets to the proper areas.
So we’re taking step one that can assist you repair these errors: as of this launch,
Help supplies a lot better errors in case your intention is known,
however one thing else is lacking (An unknown identify, space, machine class, or area).
Custom Assist responses in automations using the sentence trigger
Like almost every other component and feature of Home Assistant, Assist can be
customized and extended to understand more sentences.
A few releases ago, we introduced a very simple way to extend what Assist
understands: The sentence trigger
in our automation engine.
Up till now, utilizing a sentence set off all the time led to the identical Help response:
“Performed”. In reality, the one technique to outline a customized response was to write down advanced
customized sentences in YAML.
This launch introduces a brand new motion to set a customized response in your
sentence-triggered automations immediately contained in the automation editor.
The response discipline accepts templates, so it may be used to construct advanced
responses, for instance, itemizing all of your room temperatures.
A really cool characteristic that may turn out to be useful in case you construct an automation
blueprint to submit as an entry for our voice assistant contest!
All known Assist devices
Last addition for voice, we’ve added a small additional page to give you an
overview of all the Assist devices you have active in your Home. You can find
this on the Assist configuration dashboard
by deciding on the brand new “Help gadgets” button.
Or, use this My House Assistant button beneath to navigate to the voice assistants
configuration dashboard:
Updating your Zigbee devices
ZHA (Zigbee House Automation, our built-in Zigbee integration)
now supplies replace entities to House Assistant!
This implies you may get notified when a tool has a firmware replace accessible,
and you may set off the replace from House Assistant!
Observed the bizarre model numbers? Sadly, that’s how model numbers
within the Zigbee normal work and look. We haven’t found out a technique to translate
them to one thing extra human-readable format that matches what the producer
communicates.
Presently, it helps updating Inovelli, OSRAM/Ledvance, Sonoff, and
ThirdReality gadgets, and we’re taking a look at including help for extra manufacturers
sooner or later. Remember, Zigbee is a gradual protocol, and firmware updates can
take a very long time (typically hours).
Matter diagnostics and actions
Home Assistant works actively to provide the best support for Matter
gadgets out of the field. To assist with that, we have now added extra info and
controls in your Matter gadgets within the UI.
On the machine web page of the Matter machine in House Assistant, we are going to now present
further diagnostic details about the machine. This info might be
used to troubleshoot points with the machine or when reporting points. Some
examples embrace the community kind the machine makes use of, its addresses, and IDs,
machine sorts and its linked fabrics.
Moreover extra info, it’s also possible to take new actions on the machine.
For instance, ping the machine to verify whether it is accessible, drive a full
machine interview to sync all its info, take away it from one other controller,
and even a brand new button to share your Matter machine from House Assistant with
one other Matter controller.
Icons everywhere
We completely changed how Home Assistant handles icons under the hood.
A big effort from many people, with almost… no change! That is
right, almost everything looks just the same as before. 😁
We did make some improvements! For example, integrations can now
provide icons for things like fan speeds or thermostat presets. Also,
service call actions can now have their own icon as well:
Areas now have icons too! You can set them in the area configuration. They show
up in the area selectors and in the area dashboard itself
(in case you didn’t upload a picture).
Integrations with authentication issues are now shown in the repairs dashboards
When one of your integrations has authentication issues, Home Assistant
will now report this in the repairs dashboard.
Beforehand, this was solely seen on the combination dashboard, however now it exhibits
up within the repairs dashboard, as that is the place the place House Assistant reviews
all points along with your system.
Revamped Proximity integration
For this release, @mib1185 utterly revamped our Proximity integration.
In case you might be unfamiliar with it, it means that you can monitor the proximity of
individuals to a specific zone. It supplies info on how shut one is
to a zone and if they’re touring in the direction of or away from it.
It’s an especially highly effective device for automations. It means that you can create
automations based mostly on the proximity of individuals. For instance, if you’re inside
a sure vary from your own home and touring in the direction of it, you could possibly use
House Assistant to activate the lights, open the storage door, flip up the heating,
and begin your favourite playlist in the lounge. Welcome house! 🤗
The most effective half? This integration is now accessible to arrange from the UI!
Not simply that, but it surely now makes use of regular sensor entities that we’re all already
conversant in. It will make automating and displaying the info a breeze!
Thanks @mib1185! You probably did an impressive job on this one!
If you’re already utilizing this integration, this alteration will include the
deprecation of the previous entities. See our backwards-incompatible changes
for extra info.
Shipping on a new Python version
This release ships running on Python 3.12! In case you are wondering, what is
that? Well, Python is the programming language Home Assistant is written in.
Why it matters? It provides many improvements to the foundation we are building
Home Assistant on, most notably: It is faster! 🚀
Don’t worry! If you run the Home Assistant Operating System or are using the
Home Assistant Container installation type: You won’t have to do anything, as we
handle the upgrade to Python 3.12 for you. Just upgrade Home Assistant as
you normally would, and you are good to go! 😎
Other noteworthy changes
There are many more improvements in this release; here are some of the other
noteworthy changes this release:
-
@edenhaus improved how we deal with errors in our kind fields. We not
present the technical coding gibberish that always confirmed up prior to now. Good! - Once you change the type of a switch entity to, for instance, a storage door
entity, you’ll now have the choice to invert its conduct.
Thanks, @emontnemery! - The Ecovacs integration obtained a number of love from @edenhaus and now
has help for a lot of Deebot vacuum fashions with tons of entities to automate
with. Good job! -
@mib1185 added automated cleanups of previous/unused refresh tokens 🧹. This
means you can be logged out on a tool that hasn’t used House Assistant for
90 days. Clear and tidy! - The Tuya integration can now be arrange immediately utilizing the Tuya Sensible
or Sensible Life app. No extra want for developer accounts or sophisticated
procedures! - Utilizing the utility meter integration on, for instance, your photo voltaic inverter,
which turns off at night time? Now you can set the sensor to all the time be accessible,
even when the supply entity is unavailable. Thanks, @dougiteixeira! - The TP-Link Smart Home integration now helps newer gadgets,
together with Tapo-branded gadgets! Superior job @sdb9696, @bdraco,
and @rytilahti! -
@AngellusMortis added new sound occasion sensors launched in
UniFi Shield model 2.11 to the UniFi Protect integration. Good! - Are you a Jinja templating Ninja? @TNTLarsn added a brand new
bitwise_xor
filter so that you can use. Superior! - The Google Generative AI Conversation permits utilizing the new Gemini Pro models,
together with help for the Imaginative and prescient fashions. This lets you use pictures in your
prompts too! See an instance within the screenshot down beneath. Tremendous spectacular,
thanks @tronikos!
The Google Generative AI Dialog integration utilizing the brand new Gemini Professional Imaginative and prescient fashions to explain what’s seen on the doorbell digicam.
New integrations
We welcome the following new integrations in this release:
-
AirTouch 5, added by @danzel
Management your AirTouch 5 ducted air-con techniques. -
Bang & Olufsen, added by @mj23000
Management your Bang & Olufsen Beolab and Beosound gadgets. -
Bring, added by @miaucl
Use Deliver to create procuring lists and share them with your loved ones. -
Elvia, added by @ludeeus
Import your historic power utilization from an Elvia-operated grid. -
Epion, added by @lhgravendeel
Monitor your Epion air high quality sensors. -
Govee lights local, added by @Galorhallen
Management your Govee lights regionally. -
Home Assistant Analytics Insights, added by @joostlek
This integration means that you can monitor info from the general public and open Home Assistant Analytics. -
Hong Kong Observatory, added by @MisterCommand
Get climate info from the Hong Kong Observatory. -
Huum, added by @frwickst
Management your Huum sensible sauna heaters. -
La Marzocco, added by @zweckj
Management your La Marzocco espresso machines. -
LeaOne, added by @bdraco
Monitor your LeaOne well being machine underneath the Xiaogui and BAGAIL manufacturers. -
myUplink, added by @pajzo
Monitor myUplink-supported gadgets in House Assistant. -
Rabbit Air, added by @al-s
Regionally management and monitor your Rabbit Air air purifiers. -
Rainforest RAVEn, added by @cottsay
Pull in power information out of your Rainforest RAVEn power monitor. -
Romy, added by @xeniter
Management your Romy vacuum cleaners. -
Tedee, added by @zweckj
Use your Tedee sensible locks in House Assistant. -
Teslemetry, added by @Bre77
Pull in dwell telemetry information out of your Tesla car through the Tesla Fleet API. -
TechnoVE, added by @Moustachauve
Management of TechnoVE Sensible Charging Station utilizing a neighborhood API. -
Traccar server, added by @ludeeus
Observe your GPS gadgets by pulling information from a Traccar server.
This launch additionally has a brand new digital integration. Digital integrations are stubs
which can be dealt with by different (present) integrations to assist with findability.
The next digital integrations have been added:
Integrations now available to set up from the UI
The following integrations are now available via the Home Assistant UI:
Release 2024.2.1 – February 9
Release 2024.2.2 – February 16
Release 2024.2.3 – February 22
Release 2024.2.4 – February 25
Release 2024.2.5 – February 27
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 a wonderful place to be
at, and don’t neglect to hitch our wonderful forums.
Discovered a bug or concern? Please report it in our issue tracker,
to get it fastened! Or, verify our help page for steerage for extra
locations you’ll be able to go.
Are you extra into e-mail? Sign-up for our Building the Open Home Newsletter
to get the newest information about options, issues occurring in our group and
different information about constructing an Open House; straight into your inbox.
Backward-incompatible changes
We changed the way refresh tokens are handled. Refresh tokens are part of what
keeps you logged in to Home Assistant.
Refresh tokens will be automatically deleted when unused. A refresh token
is considered unused if it has not been used for a login within 90 days.
If your logged-in session hasn’t been used for 90 days, you will be logged out.
You will need to log in again.
We recommend using Long-lived access tokens
in case you want a everlasting token.
(@mib1185 – #108428) (documentation)
The choices circulation that gave the choice to set a customized scan interval has been
eliminated.
Adjustable scan interval is not allowed, however the possibility has
had no impact on the combination since 2023.11.
You need to use an automation as a substitute for create a customized polling fee
(documentation).
Updating one entity in a blink configuration will replace all entities in every
blink configuration.
(@mkmer – #106735) (documentation)
Replace Wi-Fi diagnostic to match new API items – beforehand Blink reported RSSI
dBm, now they report generic 0-5 for sign energy.
(@mkmer – #107539) (documentation)
This integration has been disabled. The upstream libraries utilized by
House Assistant are usually not suitable with Python 3.12.
This compatibility concern has been reported upstream.
(@frenck – #108163) (documentation)
The providers ezviz.ptz, ezviz.sound_alarm, and alarm_sound have been moved
to button and choose entities in launch 2023.8. Help for the deprecated
providers has now been utterly eliminated.
If you’re utilizing these providers in automations or scripts, you will want to
replace them to match this alteration.
(@jpbede – #107582) (documentation)
Any earlier integration setups might need to be recreated or reconfigured with
the brand new fashions/gemini-pro as a substitute of the legacy fashions/chat-bison-001.
(@tronikos – #105789) (documentation)
The Fuel meter ID sensor is eliminated and the meter ID is now proven as a serial
quantity within the machine data panel as a substitute.
(@DCSBL – #100684) (documentation)
The preset mode was returning “unknown” relatively than “none”.
Any references to preset_mode could should be up to date.
(@mkmer – #108599) (documentation)
The providers huawei_lte.clear_traffic_statistics and huawei_lte.reboot have
been moved to button entities in launch 2023.8. Help for the deprecated
providers has now been utterly eliminated.
If you’re utilizing these providers in automations or scripts, you will want to
replace them to match this alteration.
(@jpbede – #107578) (documentation)
The next sensors have been faraway from the JustNimbus integration
since they’re not accessible by means of JustNimbus’ API:
- Pump begins
- Pump hours
- Error code
- Complete replenished
- Pump circulation
- Drink circulation
The next sensors have been renamed:
- Complete saved (
total_saved) -> Complete saved (water_saved) - Complete use (
totver) -> Complete use (water_used) - Most reservoir content material (
reservoir_content_max) -> Reservoir capability (reservoir_capacity)
Automations or scripts utilizing any of the eliminated or renamed entities needs to be
up to date. As soon as up to date, the previous entities might be safely eliminated.
(@kvanzuijlen – #99212) (documentation)
The providers vacuum.turn_on and vacuum.turn_off had been deprecated in 2023.11.
Help for the deprecated providers has now been utterly eliminated.
If you’re nonetheless utilizing them, please alter your automations and scripts and
use vacuum.begin and vacuum.cease as a substitute.
(@jpbede – #107882) (documentation)
The Lutron integration beforehand created followers as gentle entities. This has been
modified to create precise fan entities as a substitute.
In case you have automations, scripts, scenes, or dashboards that used these gentle
entities, you will want to replace them to make use of the brand new fan entities.
The each day power sensors have been eliminated to stop being throttled by the
exterior API. This principally impacts ATW gadgets.
For ATA gadgets, this sensor can also be eliminated. Nonetheless, the full power consumed
(in case your machine helps that) stays accessible. The latter helps long-term
statistics, offering insights into each day power utilization through the power dashboard
or statistic card.
MQTT sensor or binary_sensor configuration with an entity_category
explicitly set to config will fail to arrange. Maintainers ought to set the
entity_category attribute to diagnostic or omit the config attribute.
(@jbouwh – #107199) (documentation)
When an MQTT entity has a tool identify equal to the entity identify or begins with
the machine identify, this can not be corrected.
When entities like these are created, they’ll have machine and entity names in
the pleasant identify. Suppose the machine identify is omitted as a result of it’s the identical
because the entity identify. In that case, the entity identify attribute needs to be null
within the JSON payload or YAML configuration.
(@jbouwh – #107188) (documentation)
The help for MQTT vacuum entities with a legacy schema is eliminated after 6
months of deprecation. Customers can use the state schema as a substitute,
which is now the default.
(@jbouwh – #107274) (documentation)
The proximity entity (proximity.*) is deprecated and shall be eliminated in 2024.8.
It’s outmoded by sensor entities.
For every tracked particular person or machine, one sensor for the space and the
course of journey to/from the monitored zone is created. Additional, for every
Proximity configuration, one sensor that exhibits the closest machine or particular person
and its distance and course of journey to the monitored zone is created.
(@mib1185 – #108730) (documentation)
The beginning time of day and begin time of night time sensors have been changed by
time entities. In the event you used these sensors in automations or scripts, you’ll
must replace them to make use of the brand new time entities.
(@jimmyd-be – #105031) (documentation)
Name to RESTful command providers will not silently fail and can increase an
exception on, for instance, timeout or decoding errors.
You can think about using continue_on_error
for scripts and automations that use RESTful instructions which can be allowed to fail
sometimes.
(@RoboMagus – #97208) (documentation)
The service vacuum.start_pause was deprecated in 2023.8. Help for the
deprecated service has now been utterly eliminated.
If you’re nonetheless utilizing this service, please alter your automations and scripts,
to make use of vacuum.pause or vacuum.begin as a substitute.
(@jpbede – #107895) (documentation)
Setting last_reset for entities with a state_class aside from complete is
not supported. Please replace your configuration if state_class
is manually configured (for instance, in templates or when utilizing customise to
override this attribute).
(@jpbede – #108391) (documentation)
The state worth of the sensor is now a standardized timestamp.
Additional, all timestamps and durations within the further fields at the moment are additionally
correct datetime/durations.
(@miaucl – [#12341064855]) (documentation)
To stop overloading the facility strips, the power information is now polled each
60 seconds. If you should ballot the info sooner, please use an automation that
calls the homeassistant.update_entity service.
(@bdraco – #104208) (documentation)
The YAML configuration for the Traccar integration has been deprecated
and shall be eliminated in House Assistant 2024.8.0. Your YAML configuration will
be mechanically imported to the brand new Traccar Server
integration.
In the event you beforehand used the scan_interval possibility, this isn’t being imported.
If you’re in want of a customized polling interval, you need to use an automation
to outline your individual customized polling conduct.
Learn more about that here.
(@ludeeus – #109226) (documentation)
Tuya has supplied a better and improved login methodology for House Assistant customers.
Having a developer account with Tuya is not required; as a substitute, you’ll be able to
scan a QR code along with your Tuya Sensible or Sensible Life app to authenticate it
with House Assistant.
After updating to this launch, House Assistant will ask you to re-authenticate
your Tuya Sensible or Sensible Life account utilizing this new methodology.
(@frenck – #109155) (documentation)
The providers vacuum.turn_on and vacuum.turn_off had been deprecated in 2023.8.
Help for the deprecated providers has now been utterly eliminated.
If nonetheless use them, please alter your automations and scripts and
use vacuum.begin and vacuum.cease as a substitute.
(@jpbede – #107896) (documentation)
Beforehand, Tuya would fall again to utilizing the metric system if the temperature
unit was not reported by a local weather machine. This conduct has been modified to
use the default unit configured in your system as a substitute.
(@DellanX – #108050) (documentation)
Since model 2023.7 you could have been knowledgeable that the “native solely” possibility of
webhooks will grow to be the default. With this launch this alteration is now put
into impact. Please, if wanted, alter your automation triggers.
(@jpbede – #107670) (documentation)
In withings, the unit of measurement of all duration-related sensors
(for instance, sleep, aim, and energetic time at the moment) has been modified from
measuring in seconds to measuring in both hours or minutes.
If you wish to measure in a unique unit, please change the
most well-liked unit of measurement within the entity settings.
The default rounding of numeric sensors to 2 decimals has been eliminated.
We now let the machine and driver resolve what precision needs to be reported. This
permits gadgets with larger precision to report precisely.
You possibly can change the show precision within the UI for the sensor or use a template
sensor if you wish to change the precision.
(@MartinHjelmare – #107100) (documentation)
Set advised precision to 0 decimals for voltage sensors with a local unit in V.
It will uniform the show precision of voltage sensors the place there in any other case
appears to be quite a lot of precision reported from completely different gadgets.
If you wish to change the precision, you are able to do that within the sensor choices within the
UI or with a template sensor.
(@MartinHjelmare – #107116) (documentation)
The Fan and Dry local weather Preset modes have been eliminated after a interval of
deprecation. In the event you haven’t performed so, it’s best to replace your automations or
scripts to make use of the corresponding Dry and Fan HVAC modes as a substitute.
(@jbouwh – #108124) (documentation)
If you’re a customized integration developer and wish to find out about breaking
modifications and new options accessible in your integration: Remember to comply with our
developer blog. The next are essentially the most notable for this launch:
Farewell to the following
The following integrations are also no longer available as of this release:
-
Facebox has been removed. It is no longer possible to get API keys,
and thus, it is no longer possible to use this integration.
(@reedy – #107005) -
Legrand House+ Management has been eliminated as their API shut down in December.
Use the Netatmo integration as a substitute for
combine your Legrand House+ Management gadgets.
(@jpbede – #107587) -
Life360 has been eliminated. They’re now actively blocking third-party
entry, together with House Assistant. The Home Assistant Companion app
is an efficient and (above all) privacy-friendly various.
(@pnbruckner – #107805)
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.2
Trending Merchandise
