Dwelling Assistant Core 2023.6! π
Prepare for a basic, old school, jam-packed launch! π€―
I’m enthusiastic about so many issues being shipped on this launch that it’s
arduous to select a favourite π
This launch has all of it.
With the ability to immediately use and again up my Dwelling Assistant configuration to my
community storage is completely unimaginable! However I additionally actually take pleasure in the brand new and
clear integrations dashboard and pages.
The function that tremendously improved the Dwelling Approval Consider my family
is unquestionably the addition of the brand new favourite colours within the mild dialogs π¨
Benefit from the launch!
../Frenck
Donβt overlook to join our release party live stream on YouTube
7 June 2023, at 12:00 PDT / 21:00 CEST!
Connect and use your existing network storage
Do you have a network storage in your home? Like a QNAP or Synology NAS?
This release adds the ability to add and use that storage with Home Assistant!
This long and highly requested feature is now available when running the
Home Assistant Operating System. In the Settings > System > Storage
menu, now you can discover a complete new set of controls to hook up with your storage
and use it to, for instance, use your community share as a media supply
in Dwelling Assistant.
Even higher: You should use it as a goal on your backups in order that when
Dwelling Assistant creates a backup for you, it would retailer it immediately on
your community storage.
A number of community storages are additionally supported; should you like, you possibly can
simply add extra.
Integrations dashboard & pages
The integrations dashboard has gotten a major overhaul!
There have been quite some usability issues with the previous version of the
integration dashboard. For example, if you use ESPHome with many units,
you might be undoubtedly acquainted with the annoying scrolling in that little card. Or,
massive error messages stretching these playing cards out, messing up the entire web page.
This launch brings in an entire new integrations dashboard that addresses many
of those points, aiming to supply a cleaner and extra constant expertise.
Gadget based mostly integrations, like ESPHome, are mixed: no extra scrolling.
A failing integration now not stretches the structure or makes the
structure βleapβ throughout retries. Customized integrations and integrations relying
on the cloud are actually extra visibly marked.
Choosing the cog icon on the mixing card will deliver you to a model new
integrations web page, exhibiting all details about the mixing:
Within the above instance, the ESPHome integration web page reveals all units
this integration has. All the data and choices, beforehand squashed into
the mixing dashboard, are actually obtainable right here.
These model new integration pages are useful in different places in Dwelling Assistant.
For instance, the system pages can now hyperlink again on to the mixing
that supplied it.
Light entity dialog improvements: favorite colors
Recently we introduced new controls in the light entity dialog, and this release
iterates on the design by adding the current brightness, new controls,
and adding favorite colors! π¨
Each light (or light group) has its own set of colors. These colors can
be added, changed, removed, and reorganized using drag-and-drop. To enter
edit mode, select and hold one of the colors:
Added to the entity dialog: last changed
By popular request, the information on when an entity was last changed has
been added back to the new entity information dialogs.
Not only that, @piitaya added a really good easter egg! You may click on on it
to toggle between the relative and absolute format!
Related information
Which automation is using that blueprint? Well, Home Assistant can now tell you
that! On the Settings > Automations & Scenes > Blueprints
web page, choose the three dotted menu on any blueprint to find which
automations are utilizing that blueprint.
Not solely that, should you by chance attempt to take away a blueprint that’s nonetheless in use,
Dwelling Assistant will cease you from eradicating it and inform you which automations
nonetheless depend on it.
Maintain on; there’s extra associated! The associated gadgets within the entity info
dialog have been improved as nicely. The outdated record of hyperlinks is gone, and it now reveals
a far more fashionable view of all associated gadgets for an entity:
Discover the way it properly hyperlinks again to the brand new integration web page right here too!
Copy βn paste support in the automation editor
An amazing contribution by @karwosts on this launch that provides reduce, copy
& paste capabilities to the automation and script editors!
Now you can copy and paste any set off, situation, and motion into completely different
locations of your automation and even paste it into a unique automation
altogether!
Python 3.11 and significant performance upgrades
This release ships running on Python 3.11! In case you are wondering, what is
that? Well, Python is the language the Core of Home Assistant is written in.
Why it matters? It is seriously faster! π
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.11 for you.
And that is not all in terms of performance. Weβve also upgraded internal parts,
including a newer SQLite version that should be faster. Oh! And, of course,
@bdraco has been everywhere to optimize rather a lot (rather a lot lot).
This launch might be anticipated to be rather a lot sooner (or much less consuming) of assets
at runtime.
Matter 1.1
The Matter implementation within Home Assistant is now based on the freshly
released 1.1 version of the Matter standard. This brings a ton of stability
fixes and improvements, but unfortunately, no new features.
Thanks to @Diegorro98, we do now have help for tilt covers! In addition to that,
this Dwelling Assistant launch ships with a number of generic bugfixes and
optimizations; weβve managed to squeeze out some further efficiency to
make state updates on your Matter units lightning-fast π
All these stability enhancements to each the Matter stack and our
implementation didn’t go unnoticed:
Z-Wave updates
There has been quite a bit of progress on Z-Wave in Home Assistant.
Thanks to @raman325, the mixing reached platinum degree π on our
high quality scale. This implies the mixing now does issues proper in accordance
to finest practices which ought to imply a greater person expertise usually.
Have you ever ever turned on a Z-Wave mild from the Dwelling Assistant UI simply to see
the toggle going off once more after a few seconds, then after some extra
seconds seeing it going again to on? This long-standing concern (that even acquired the
nickname flip/flop) for sure units, which are sluggish to reply to their
state has lastly been addressed.
For these of you that wish to automate every thing, now you can automate not
solely the Z-Wave system state but in addition the system configuration. We added system
configuration parameter entities so that just about each Z-Wave system setting
is now obtainable as an entity.
Not stopping there, we additionally added entities for system connection statistics,
which you need to use to, for instance, create a notification if a tool generates
greater than a specific amount of dropped messages. If you wish to monitor
a misbehaving system, you possibly can allow these sensors to view the historical past
of the connection efficiency.
Within the background, @AlCalzone is working tirelessly on the Z-Wave JS driver,
which is the muse of our Z-Wave integration. Amongst different issues, some
units are actually sooner to interview throughout addition, and extra units
might be configured.
New entities! Date, time, date/time
We welcome three new entity sorts on this launch:
date
, time
& datetime
.
These entities allow integrations to provide date, time, or date/time input
controls from the UI. They are very similar to the input datetime
helper but are available for use by integrations.
How the new time, date, and date/time entities will look like on your dashboards.
They are so new that no integrations are using them yet, but you can expect
to see usage in (custom) integrations of these soon!
Thanks for creating those @raman325!
Other noteworthy changes
There are much more easter bunnies in this release; here are some of the other
noteworthy changes this release:
- When using services in the UI (like in the automation editor), only options
and settings available to the selected target devices & entities will be shown.
This makes the UI much cleaner! Thanks, @emontnemery and @bramkragten! - The Roborock integration (launched within the earlier launch) obtained a lot
love and now gives a variety of recent entities. Thanks @Lash-L! - The Android TV Distant integration now gives a media participant entity too!
Good, @Drafteed! -
KNX now gives its personal panel, permitting you to add your KNX
mission file, and provides a bunch monitor for stay bus diagnostics.
Data from the mission can be used for system triggers.
Superb @marvin-w and @farmio! -
@bdraco added the choice to disable Webhooks for ONVIF in case your
digicam isnβt totally following specs. - The variables motion is now additionally obtainable within the automation and script
editors within the UI. Thanks, @piitaya - The add-on dashboard now has a search bar. Useful, @bramkragten!
- The Samsung TV now has a distant entity, permitting you to ship distant key
presses on to your TV! Thanks @peitschie! - The States in the developer tools now
makes use of the entity ID within the entity ID picker. Thanks, @bramkragten! -
@gjohansson-ST added a service to vary a working timer helper, @frenck
did one thing comparable and added a service to set the worth of a counter helper. - The AccuWeather integration now gives sensors for the climate situation
and photo voltaic irradiance values. Thanks, @bieniu - Now you can replace your QNAP QSW immediately from Dwelling Assistant. Good @Noltari!
- The BMW Related Drive now permits you to toggle local weather on/off and new
entities associated to the charging of your automobile. Thanks, @rikroe and @cpoulsen!
New Integrations
We welcome the next new integrations on this launch:
-
Airzone Cloud, added by @Noltari
Local weather management on your Aidoo, Easyzone, or Flexa air conditioners. -
Date, Time, and Date/Time, added by @raman325
New entity sorts that enable integrations to supply date/time controls. -
Electra Good, added by @jafar-atili
Management your Electra Air air conditioner from Dwelling Assistant. -
Google Generative AI Dialog, added by @tronikos
A dialog agent powered by Google Generative AI. -
JVC Projector, added by @SteveEasley
Now you can automate your community controllable JVC Projector. -
YouTube, added by @joostlek
Add your favourite YouTube channels as sensors.
This launch additionally has a brand new digital integration. Digital integrations
are stubs which are dealt with by different (current) integrations to assist with
findability. This one is new:
Integrations now obtainable to arrange from the UI
The next integrations are actually obtainable through the Dwelling Assistant UI:
Release 2023.6.1 – June 8
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 concern? Please report it in our issue tracker,
to get it mounted! Or, verify our assist web page for steerage for extra
locations you possibly can go.
Are you extra into e mail? Signal-up for our Constructing the Open Dwelling Publication
to get the most recent information about options, issues taking place in our neighborhood and
different information about constructing an Open Dwelling; straight into your inbox.
Breaking Changes
All Home Assistant versions, of which the Home Assistant project manages the
Python version for you, have been upgraded to Python 3.11. This affects
the following installation types:
- Home Assistant Operating System
- Home Assistant Container
- Home Assistant Supervised
This might affect you when using custom integrations, as those must be
compatible with Python 3.11.
Furthermore, as of this release, Python 3.10 is deprecated, and support will
be removed in Home Assistant 2023.8. This only affects you if you are
running Home Assistant Core installation type in your own Python virtual
environment. Please update your Python version to Python 3.11.
If you run Home Assistant OS, Home Assistant Container, or Home Assistant
Supervised, we have taken care of this for you; you will be using Python 3.11
automatically on upgrade.
The counter
entities now not restore their earlier manually set
configuration (utilizing the – now deprecated – counter.configure
service) on
Dwelling Assistant startup. As an alternative, it would now use the configuration as set in
the helper configuration within the UI (or as configured YAML, if used).
This habits is eliminated, because it brought about configuration points, as the brand new
configuration was by no means utilized once more (however ceaselessly restored). This habits was
out of the peculiar for Dwelling Assistant and thus now standardized.
The worth of the counter remains to be restored and obtainable throughout Dwelling Assistant
restarts.
The Command Line integration modifications its YAML configuration format from
an old-style platform configuration to a extra fashionable integration-style
configuration format.
For instance, you probably have a binary sensor configured beforehand as:
# Instance configuration.yaml entry
binary_sensor:
- platform: command_line
command: "cat /proc/sys/internet/ipv4/ip_forward"
That very same binary sensor is now configured beneath the command_line
integration
configuration as:
# Instance configuration.yaml entry
command_line:
- binary_sensor:
command: "cat /proc/sys/internet/ipv4/ip_forward"
Be aware: Whereas that is at present not but a breaking change, it did increase questions
throughout our beta testing interval. Therefore we have now added this as a breaking change
to supply extra context.
(@gjohansson-ST – #92824) (documentation)
The beforehand deprecated YAML configuration of the D-Hyperlink Wi-Fi Good Plugs
integration has been eliminated.
D-Hyperlink Wi-Fi Good Plugs are actually configured through the UI. Any current YAML
configuration has been imported in earlier releases and might now be safely
eliminated out of your YAML configuration information.
(@gjohansson-ST – #92590) (documentation)
The beforehand deprecated YAML configuration of the EDL21
integration has been eliminated.
EDL21 is now configured through the UI. Any current YAML
configuration has been imported in earlier releases and might now be safely
eliminated out of your YAML configuration information.
(@gjohansson-ST – #93551) (documentation)
The binary sensor offering βimprove obtainableβ info has been eliminated
and changed by a brand new replace
entity. If you happen to use the binary sensor in your
automations, scripts, or dashboards, you will have to regulate them to
this transformation.
(@RenierM26 – #85377) (documentation)
The beforehand deprecated YAML configuration of the Frontier Silicon
integration has been eliminated.
Frontier Silicon is now configured through the UI. Any current YAML
configuration has been imported in earlier releases and might now be safely
eliminated out of your YAML configuration information.
(@gjohansson-ST – #93552) (documentation)
The Google Nest YAML configuration has been totally eliminated. It’s best to make sure you
have imported your configuration and credentials into the UI earlier than upgrading.
Nest Desktop or OOB authentication, which was beforehand disabled by Google,
has now been eliminated.
(@allenporter – #92311) (documentation)
Dwelling Assistant was nonetheless utilizing the legacy Python pip bundle resolver, which
has been eliminated. As a consequence of upstream bundle conflicts, the IBM Watson TTS
integration has been disabled.
The upstream mission offering the libraries used has been notified repeatedly
in, at the very least, the previous two years; sadly, with out response. We had no
different selection than to disable this integration.
(@frenck – [#92124]) (documentation)
The default unit of measurement for manually arrange sensors from IHC has been
eliminated. Dwelling Assistant now assumes all sensors with a unit of measurement set
are a quantity. IHC sensors might be textual content, however due to the default unit of
measurement, there’s at present no strategy to get textual content sensors from IHC working.
This can be a breaking repair as a result of should you at present have temperature sensors
and not using a unit of measurement set, you’ll have to set this for the sensors.
LG Netcast media gamers now not have faux (assumed) taking part in
or paused
states, and people are changed with the on
state.
If you happen to used the taking part in
or paused
state in your automations, you will have
to replace them to match this transformation.
The beforehand deprecated YAML configuration of the Nextcloud
integration has been eliminated.
Nextcloud is now configured through the UI. Any current YAML
configuration has been imported in earlier releases and might now be safely
eliminated out of your YAML configuration information.
(@gjohansson-ST – #93550) (documentation)
The beforehand deprecated YAML configuration of the Obihai
integration has been eliminated.
Obihai is now configured through the UI. Any current YAML
configuration has been imported in earlier releases and might now be safely
eliminated out of your YAML configuration information.
(@gjohansson-ST – #93549) (documentation)
Persistent notifications are now not saved within the state machine. This implies
that we now not create an entity for every persistent notification.
If you happen to used these entities in, for instance, automations, scripts, or templates,
you gainedβt be capable of use these anymore.
(@bdraco – #92828) (documentation)
The persistent_notification.mark_read
service has been eliminated.
The beforehand deprecated YAML configuration of the Rain Chicken
integration has been eliminated.
Rain Chicken is now configured through the UI. Any current YAML
configuration has been imported in earlier releases and might now be safely
eliminated out of your YAML configuration information.
(@gjohansson-ST – #92599) (documentation)
The beforehand deprecated rainbird.rain_delay
service for Rainbird has been
eliminated. Please replace any automation or script relying on this service.
(@gjohansson-ST – #92601) (documentation)
Dwelling Assistant was nonetheless utilizing the legacy Python pip bundle resolver, which
has been eliminated. As a consequence of upstream bundle conflicts, the Salda Smarty
integration has been disabled.
The upstream mission offering the libraries used has been notified repeatedly
in, at the very least, the previous two years; sadly, with out response. We had no
different selection than to disable this integration.
(@frenck – [#92124]) (documentation)
The beforehand deprecated YAML configuration of the Samsung Good TV
integration has been eliminated.
Samsung Good TV is now configured through the UI. Any current YAML
configuration has been imported in earlier releases and might now be safely
eliminated out of your YAML configuration information.
The tampered and low battery standing zone attributes have been moved into their
personal devoted binary sensors. If you happen to use these attributes in your automations,
scripts, or dashboards, you will have to replace these to replicate this transformation.
(@austinmroczek – #73152) (documentation)
The beforehand deprecated YAML configuration of the Vallox
integration has been eliminated.
Vallox is now configured through the UI. Any current YAML
configuration has been imported in earlier releases and might now be safely
eliminated out of your YAML configuration information.
On/Off properties for the Indicator CC are now not found as entities.
They have been beforehand found as sensor entities which weren’t helpful in
instances the place you needed to vary these values, and also you would wish to vary
the worth for all three On/Off properties concurrently to ensure that them to
work, which wasnβt supported with our current discovery mannequin.
(@raman325 – #90248) (documentation)
For units with the Entry management
generic system class, the Door lock mode
config parameter now not will get created as a sensor
entity and can as a substitute
get created as a choose
entity.
(@raman325 – #92223) (documentation)
The Good IBT4ZWAVE module was beforehand found as a lightweight, however now it’s
found as a canopy. The sunshine entity will likely be completely unavailable and might
be safely deleted.
(@raman325 – #93946) (documentation)
You probably have zwave_js cowl entities already and your system helps Window
Protecting CC, you may even see newly created cowl entities. The outdated cowl entities
can safely be deleted, however all customizations have to be reapplied to the
new entities.
In case you are a customized integration developer and need to study breaking
modifications and new options obtainable on your integration: Make sure you comply with our
developer blog. The next are probably the most notable for this launch:
Farewell to the following
The following integrations are also no longer available as of this release:
All modifications
In fact, there’s much more on this launch. Yow will discover a listing of
all modifications made right here: Full changelog for Dwelling Assistant Core 2023.6