House Assistant Core 2022.7! ☀️
This was one thrilling and busy month! In case you’ve missed it, there was
a Matter in House Assistant workshop
and a Let’s get loud! occasion
about bringing audio to the Open House.
If in case you have missed these, it’s worthwhile to examine these recordings out.
In the meantime, preparations are occurring for the upcoming Matter and naturally,
the soon-to-be-released House Assistant Yellow! 💛 Extra about that quickly™.
This launch is unquestionably representing the “streamlining experiences”
motto we’ve got been utilizing. The efficiency enhancements on this launch are
as soon as extra: gorgeous! Moreover, there are some great new options to
discover too.
This launch has the right combine! I’m certain there’s something in right here you
like. So with out additional due: Benefit from the launch!
../Frenck
Don’t overlook to be a part of our launch celebration reside stream on YouTube at present at 12:00 PDT / 21:00 CET!
Improved stability and efficiency, and Python 3.10
The hunt to enhance the efficiency of House Assistant continues. For a lot of
releases, @bdraco has been analyzing each single facet of
House Assistant and manages to make it sooner each single launch.
Often, we’ve got a piece on the finish of our launch notes informing you
in regards to the efficiency enhancements made. The enhancements on this launch,
nonetheless, are an enormous deal.
Our YAML & JSON tooling improved, utilizing sooner libraries and strategies.
JSON is used internally and for communication with the frontend, which is
A LOT snappier now. When you use a lot of YAML, you’ll undoubtedly discover this
when beginning House Assistant or reloading issues like your automations 🚀.
Units with an integration error throughout startup that may self-recover
will now try this immediately as quickly because the machine is found.
We now use a greater and sooner encryption methodology for the HomeKit Accent
Protocol (HAP). It improves the efficiency of the HomeKit, HomeKit Controller,
and Apple TV integrations and prepares House Assistant for iOS 16.
Lastly, @pvizeli has been working arduous to ship House Assistant on Python 3.10!
Which additionally brings fairly a efficiency enchancment. When you run the House Assistant
Working System or use our container set up methodology, you’ll
robotically get this; there isn’t a must do something. 🚀
Replace Z-Wave gadgets instantly from House Assistant
All software program has bugs, together with the software program in your Z-Wave gadgets. However how
to replace these? Don’t have any worry! As of at present, we’ve got an answer for this!
Because of the arduous work and collaboration between @AlCalzone from Z-Wave JS
and @raman325 from House Assistant, now you can set up updates in your
Z-Wave gadgets instantly from the House Assistant interface!
On the machine web page of your Z-Wave machine, there’s now a menu merchandise permitting
you to put in Z-Wave firmware updates onto your machine manually.
Get a software program replace on your Z-Wave machine from the producer,
and begin an replace in House Assistant, which lets you add the
replace file you bought from the producer. The remainder is pure magic!
Throughout replace set up, you’ll be introduced with the replace’s progress.
It’s that straightforward 💪
The about web page is now stunning too!
Have you ever ever appeared on the about web page within the House Assistant settings menu?
It was in all probability one of many least visually interesting pages nonetheless in our menus,
and @zsarnett appeared to agree. He made it much more cleaner and useful.
It now clearly reveals the variations of the totally different parts your occasion is
made up of, and gives a clear menu to every kind of House Assistant associated
hyperlinks.
Change any climate unit to your choice
House Assistant has many climate companies that may be built-in; it’s
nice to have a alternative! The variations between these are sometimes their
accuracy on your area and the models of measurement used for the
totally different climate information factors.
However what for those who’d just like the barometric stress unit to be in mbar as an alternative of
hPa? Or perhaps use m/s or knots as an alternative of km/h for wind velocity? No downside!
Now you can change the models every climate entity makes use of! Not simply temperature,
however for the entire values a climate entity gives. When altering a unit,
House Assistant will care for changing the values for you.
On the same be aware, quantity entities that characterize a temperature at the moment are transformed to
the temperature unit utilized by the configured unit system.
Thanks @emontnemery and @gjohansson-ST for including this and updating
all current climate integrations to help this 👍.
Labels as an alternative of values for gauge playing cards segments
When displaying an entity gauge card in your dashboard, it could present the
gauge with the sensor worth. For instance, for those who’d use a humidity sensor,
it reveals the humidity proportion in the midst of the gauge.
Within the 2022.5 launch, we added phase help to our gauge card.
On this launch, @kristjanbjarni added label help to these segments!
Which means in case your phase has a label, the gauge card will present
that label as an alternative of the sensor worth when it’s in that vary.
For extra data, take a look at our gauge card documentation.
Code editors now auto-complete MDI icons
All of our code editors within the frontend now have auto-completions for
MDI icons. Simply begin typing mdi: and it’ll make it easier to discover the precise icon
you want.
Like the conventional icon picker, it helps looking out on components of the icon
title, its aliases and classes. Moreover, it would present a little bit preview
of the icon you might be about to pick, so you recognize you bought the precise one.
Thanks @bramkragten, this can be a very nice addition!
Filter the historical past panel
If in case you have a lot of gadgets and entities then the
historical past panel may be lengthy! Truly,
it could change into so massive, that it turns into unpractical. You might at all times
filter it right down to a single entity, however that’s pretty restricted as properly.
For this launch, @D3v01dZA improved these filters.
The historical past can now be filtered by a number of entities, by all entities of
a number of areas, or by all entities of a number of gadgets.
That is tremendous useful, as now you can view the historical past of all entities in,
for instance, your front room space fast and straightforward.
Simply convert values to booleans in templates
If you’re into templates, @pyos has a shock for you: We now have a bool
operate that can be utilized as a filter too!
If you’re a bit into coding, this isn’t the usual bool(), however one which
could be very particular for House Assistant, making it very helpful.
This bool methodology converts a price right into a boolean and considers
House Assistant’s particular guidelines for truthy values. Some examples: "on" will
be thought of true, and "disabled" shall be thought of false.
Utilizing bool as a filter and mixed with and iif
filter, you’ll be able to rapidly change, for instance, binary sensors values into any
textual content you’d like.
For extra data, take a look at our Templating documentation.
Different noteworthy adjustments
There may be far more juice on this launch; listed below are among the different
noteworthy adjustments this launch:
- The Materials Design Icons have been up to date to v6.9.96, providing you with
100 and one other
100 model new icons
to make use of 🤩 . - Now you can management the loudness and varied extra surround-related
settings of your Sonos audio system, thanks @jjlawren! 🔊 - Now you can set off Alexa routines from switches, toggles, and buttons
with out the necessity to wrap them right into a binary template sensor first.
Incredible addition, @mdegat01! - The logbook reside feeds will now robotically pause if you begin
scrolling and resume when you find yourself again on the prime once more. Thanks, @bdraco! -
@matrixd2 prolonged YoLink; It now helps thermostats, valve controllers,
locks, and vibration, CO, and Smoke Sensors! - Jellyfin now helps film collections within the media browser, thanks @j-stienstra!
- Because of @dmulcahey, the extensively mentioned Aqara FP1 sensor is now
supported by ZHA! -
@ghedo has been busy bettering the Space Card. It will probably now present
moisture/flood alerts, humidity, and reveals an icon for temperature. Good! -
@kingy444 added help for High/Down, Backside/As much as Hunter Douglas PowerView.
Moreover, buttons to calibrate and jog (determine) have been added. @bdraco
added help for polling in case the machine is mains powered. - Because of @thrawnarn, now you can ship polls through Telegram bot!
- The House Join integration now has entire assortment of recent companies
that can be utilized to regulate and configure choices of machine applications.
Very nice, @BraveChicken1! - If in case you have WiZ energy plugs with energy monitoring, these at the moment are supported,
due to @bdraco ⚡️. -
@gjohansson-ST added a lot of like to Sensibo this launch. Assist for
(cut up) timers, Pure Enhance, enhancements to setting temperature, bug fixes,
and plenty of extra. Good work! -
@iAutom8 made his first-time-ever open supply contribution ❤️; And added
help for added temperature sensors in ViCare.
New Integrations
This launch doesn’t embody new integrations.
Integrations now accessible to arrange from the UI
The next integrations at the moment are accessible through the House Assistant UI:
Launch 2022.7.1 – July 7
Launch 2022.7.2 – July 8
Launch 2022.7.3 – July 10
Launch 2022.7.4 – July 13
Launch 2022.7.5 – July 14
Launch 2022.7.6 – July 20
Launch 2022.7.7 – July 26
Need assistance? Be a part of the group!
House Assistant has a terrific group of customers who’re all greater than keen
to assist one another out. So, be a part of us!
Our very lively Discord chat server is a superb place to be
at, and don’t overlook to hitch our superb boards.
Discovered a bug or situation? Please report it in our situation tracker,
to get it mounted! Or, examine our assist web page for steering for extra
locations you’ll be able to go.
Are you extra into e-mail? Signal-up for our Constructing the Open House E-newsletter
to get the most recent information about options, issues occurring in our group and
different information about constructing an Open House; straight into your inbox.
Breaking Adjustments
Under is a list of the breaking change for this launch, per topic or
integration. Click on on a kind of to learn extra in regards to the breaking change
for that particular merchandise.
House Assistant now ships with Python 3.10 for the next set up strategies:
- House Assistant Working System
- House Assistant Container
- House Assistant Supervised
You don’t should do something; this may all occur robotically. Nevertheless,
this is likely to be a breaking change in case you might be utilizing customized integration
that doesn’t help Python 3.10 but.
(@pvizeli – #73830) (documentation)
House Assistant is upgrading to Python 3.10 this launch and comes
with a breaking change affecting a number of integrations.
Identified affected integrations on the time of writing:
These integrations depend on the bluepy and pybluez libraries, which now not
work in newer variations of Python. bluepy has seen its final replace in
December 2018 and hasn’t
saved up with adjustments within the Python world.
Related story with pybluez.
We are able to’t mitigate this situation. If you’re utilizing certainly one of these integrations,
these will now not work. We reasonably needed to see a non-breaking answer,
however we noticed no backward suitable path or different options to assist this.
If you want to assist repair or improve certainly one of these integrations, we
could be grateful. We suggest migrating these integrations onto the
Bleak library as an alternative.
(@pvizeli – #73830) (documentation)
All entity filters, as utilized by the next integrations:
Have been adjusted to make entity filters deal with contains stronger than excludes.
Filters at the moment are utilized as follows when there are area and glob contains
(may have excludes):
- Entity listed in entities embody: embody
- In any other case, entity listed in entities exclude: exclude
- In any other case, entity matches glob embody: embody
- In any other case, entity matches glob exclude: exclude
- In any other case, entity matches area embody: embody
- In any other case: exclude
(@bdraco – #74080) (documentation)
This is applicable to all (climate) integrations offering climate entities.
Beforehand the models for Climate had not been corresponding appropriately with
the documentation. These models at the moment are aligned for stress and wind velocity:
- If the unit system is metric, the default stress unit is
hPa,
and the default wind velocity unit iskm/h. - If the unit system is imperial, the default stress unit is
inHg,
and the default wind velocity unit ismi/h.
The Eight Sleep integration migrated to configuration
through the UI. Configuring Eight Sleep through YAML configuration
has been deprecated and shall be eliminated in a future House Assistant launch.
Your current YAML configuration is robotically imported on improve to this
launch; and thus may be safely eliminated out of your YAML configuration
after upgrading.
(@raman325 – #72570) (documentation)
The beforehand deprecated YAML configuration of the Glances
integration has been eliminated.
Glances 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 recordsdata.
(@engrbm87 – #72706) (documentation)
The Google Calendar google.scan_for_calendars service has been eliminated.
Related performance may be achieved with the
homeassistant.reload_config_entry service, which is able to reload the
integration and cargo all new calendars from the API.
(@allenporter – #73010) (documentation)
The Google Calendar add_event service is deprecated and shall be eliminated in
a future House Assistant launch.
A brand new service create_event with equal performance is its substitute,
which is an entity-based service that takes an entity as a goal
(reasonably than a Google Calendar ID).
(@allenporter – #72473) (documentation)
Google Calendars now not helps entity customizations within the UI
when google_calendars.yaml specifies the identical entity a number of occasions.
(@allenporter – #73715) (documentation)
High Down/Backside Up shades will now have an entity to regulate every motor.
You have to to manually take away any outdated entities by deciding on the unavailable
entities from the House Assistant Interface, deciding on “REMOVE ENTITY”, and
then confirming the removing by clicking “REMOVE”.
- If in case you have automations to set shade place primarily based on entity ID, you’ll
must reconfigure these as the brand new entities shall be named otherwise. - When you solely have automations set to set off scenes you don’t must
reconfigure automations.
(@kingy444 – #62788) (documentation)
The beforehand deprecated YAML configuration of the Islamic Prayer Occasions
integration has been eliminated.
Islamic Prayer Occasions 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 recordsdata.
(@engrbm87 – [#7287248332]) (documentation)
The Kostal Plenticore now has quantity entities. Two current sensors entities
have been promoted to this platform: “Battery min Soc” and
“Battery min House Consumption”.
When you use these sensors entities in your automation, scripts, or dashboards,
you will want to regulate these for this transformation.
(@stegm – #64927) (documentation)
The LG Soundbars integration migrated to configuration
through the UI. The automated discovery of the combination through legacy discovery
has been eliminated.
This modification has no doable migration path; due to this fact, for those who use this
integration, you’ll have to re-add it manually through the person interface.
Overview
The Life360 integration has been transformed from the outdated “legacy”
implementation (which makes use of known_devices.yaml) to the newer entity primarily based
design, just like what was executed again within the 0.94.0 launch to many different
machine tracker integrations.
On account of this transformation, all of your current Life360 entities will change into
non-functional, and there shall be new entities, with totally different entity IDs,
that are useful.
Steps to switch outdated entities with new ones
- Edit the
known_devices.yamlfile in your configuration listing to
take away any Life360-related entries. Or, if there are solely Life360 entries in
this file, merely delete the file solely. - Restart House Assistant. All of the outdated, non-functional Life360 entities
ought to now be gone. (If you’re nonetheless seeing the outdated entities, strive refreshing
your browser.) - Go to the Entities web page (beneath Settings -> Units & Providers -> Entities)
and alter the entity IDs for the brand new Life360 entities as desired.
Eliminated/modified performance
The beforehand deprecated YAML configuration of the Life360
integration has been eliminated.
Life360 is now configured through the UI. Any “superior” choices in
YAML configuration shall be imported. As soon as the migration is full,
any life360 entries in YAML configuration must be eliminated.
The next choices are now not supported:
circlesmemberserror_thresholdwarning_threshold-
max_update_wait(together with thelife360_update_overdue&life360_update_restoredoccasions) show_as_state: shifting
Moreover, the next entity attributes have been modified:
- Renamed:
battery->battery_level - Eliminated:
shifting,raw_speed
If in case you have been utilizing these attributes in your automations or script, you’ll
must adapt them to this transformation.
(@pnbruckner – #72461 #73904) (documentation)
The start_engine, stop_engine, turn_on_hazard_lights,
turn_off_hazard_lights, start_charging, and stop_charging companies are
faraway from the Mazda integration.
They had been deprecated in 2022.4 and changed by button and change entities.
(@bdr99 – #73403) (documentation)
Met Workplace doesn’t present exact visibility distance, solely ranges – i.e.,
one thing like “Superb – 20-40 km”.
This doesn’t match into the climate entity mannequin, so it’s now eliminated.
The outdated worth remains to be accessible in a separate sensor supplied
by this integration.
(@avee87 – #74314) (documentation)
The beforehand deprecated YAML configuration of the Mikrotik
integration has been eliminated.
Mikrotik 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 recordsdata.
(@engrbm87 – #72581) (documentation)
The beforehand deprecated YAML configuration of the MySensors
integration has been eliminated.
MySensors 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 recordsdata.
The Nest authentication methodology referred to as “Desktop”, “Put in App” or “OOB” auth
has been deprecated
by Google and is scheduled to interrupt current customers in October.
Consequently, the House Assistant Nest integration setup has been streamlined
to assist make the transition simpler for customers. See the combination
documentation for particulars.
The configuration of the OAuth software credentials for the Nest integration
has migrated to configuration through the UI. Configuring Nest OAuth software
credentials through YAML configuration has been deprecated and shall be eliminated in
a future House Assistant launch.
When you had been already utilizing Net Auth, your current Nest software credentials
within the YAML configuration are robotically imported on improve to this launch;
and thus may be safely eliminated out of your YAML configuration after upgrading.
(@allenporter – #73050) (documentation)
The beforehand deprecated YAML configuration of the Notifications for
Android TV / Fireplace TV integration has been eliminated.
Notifications for Android TV / Fireplace TV is now configured through the UI,
any current YAML configuration has been imported in earlier releases and
can now be safely eliminated out of your YAML configuration recordsdata.
(@engrbm87 – #73227) (documentation)
The beforehand deprecated YAML configuration of the NZBGet
integration has been eliminated.
NZBGet 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 recordsdata.
(@epenet – #72424) (documentation)
The Radio Thermostat integration migrated to configuration
through the UI. Configuring Radio Thermostat through YAML configuration
has been deprecated and shall be eliminated in a future House Assistant launch.
Your current YAML configuration is robotically imported on improve to this
launch; and thus may be safely eliminated out of your YAML configuration
after upgrading.
(@bdraco – #72874) (documentation)
Radio Thermostat’s maintain mode is now configured utilizing a change. This replaces
the unique YAML configuration choice named hold_temp.
The mixing now solely synchronizes time when loaded if the maintain mode
shouldn’t be lively. Synchronizing the time when the maintain mode is lively causes
the maintain mode to disable unexpectedly.
(@bdraco – #73104) (documentation)
The default scan interval of the scape sensor has been modified from 30 seconds
to a extra affordable 10 minutes; This prevents unneeded hammering of
web sites by default.
(@balloob – #74285) (documentation)
The Simplepush integration migrated to configuration
through the UI. Configuring Simplepush through YAML configuration
has been deprecated and shall be eliminated in a future House Assistant launch.
Your current YAML configuration is robotically imported on improve to this
launch; and thus may be safely eliminated out of your YAML configuration
after upgrading.
(@engrbm87 – #73471) (documentation)
The SkyBell integration migrated to configuration
through the UI. Configuring SkyBell through YAML configuration
has been deprecated and shall be eliminated in a future House Assistant launch.
Your current YAML configuration is robotically imported on improve to this
launch; and thus may be safely eliminated out of your YAML configuration
after upgrading.
After upgrading, every Skybell will now have a tool for every doorbell.
Additionally, it has change into pointless to prefix all entities with “SkyBell”,
this will change you current entities after upgrading and it’s essential to modify
your automation, scripts and dashboard for this transformation.
(@tkdrob – #70887) (documentation)
The next SkyBell entity attributes have been cut up out into their very own
sensors: final movement occasion, final button occasion, final check-in, movement threshold,
video profile, Wi-Fi SSID, Wi-Fi standing.
When you depend on these attributes in your automations or scripts, you will want
to adapt them to this transformation.
(@tkdrob – #73089) (documentation)
The next energy entity attributes from the local weather entity for SmartThings
Air Conditioner have been eliminated and added as separate sensors:
power_consumption_startpower_consumption_endpower_consumption_powerpower_consumption_energy
When you presently use these attributes in your automation or scripts,
you’ll must adapt them to this transformation.
(@mbo18 – #72594) (documentation)
GSM sign sensor entity was changed with a set of extra granular ones.
The outdated entity will change into unavailable after updating to this launch.
(@PaulAnnekov – #70486) (documentation)
- This integration now requires System Bridge 3.1.2 and above. Any older
model will now not work. - BIOS Model, Idle, System, and Consumer Load sensors have been eliminated.
These are now not accessible from System Bridge information modules. - Command service has been eliminated. This has been faraway from System Bridge
because of potential safety points. - Open path and URL at the moment are separate companies. If you’re utilizing the
outdatedsystem_bridge.openservice, you will want to replace your
automation to make use of the brand new service(s). - GPU entities are from a brand new supply, so they might have modified names barely.
Any automations utilizing these entities could should be up to date. - GPU fan velocity is now measured in RPM as an alternative of %.
(@timmo001 – #71218) (documentation)
The beforehand deprecated YAML configuration of the Tautulli
integration has been eliminated.
Tautulli 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 recordsdata.
(@ludeeus – #74172) (documentation)
Entity attributes of Tautulli entities have now been moved to their very own sensors.
When you presently use these attributes in your automation or scripts,
you’ll must adapt them to this transformation.
(@tkdrob – #71712) (documentation)
The beforehand deprecated YAML configuration of the Transmission
integration has been eliminated.
Transmission 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 recordsdata.
(@engrbm87 – #72832) (documentation)
The brand new disk sensors pull from utterly totally different information than the outdated ones.
They need to be largely suitable for performance, however orphaned sensors could
nonetheless be created. Any orphaned sensors may be safely deleted.
The sensors’ naming format has additionally modified to match what’s proven in UniFi
Defend. Moreover, the additional state attribute for the mannequin has
been utterly eliminated since now the slot numbers match what UniFi
Defend shows.
(@AngellusMortis – #73104) (documentation)
Entities that supplied an “edit” configuration interface for Defend gadgets
(just like the HDR Swap or Recording Mode Choose) have all now been changed by
common sensor entities; for those who would not have write entry to that UniFi Defend
Gadget.
These switches, choose entities, and so forth., by no means really labored beforehand since
the person didn’t have permission to vary them, however you could possibly learn the standing.
Any entities which are orphaned by this may be safely deleted.
An “order of significance” between the states of the kids of
Common Media Participant has been added. The lively media participant would possibly change
if among the kids are in “taking part in” and “paused” states,
relying on the kids’s order.
(@koying – #68036) (documentation)
The beforehand deprecated YAML configuration of the UPnP/IGD
integration has been eliminated.
UPnP/IGD 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 recordsdata.
(@epenet – #72410) (documentation)
The air_quality and filter_life attributes have been faraway from the fan
entities. Devoted sensor entities have changed these attributes.
If you’re presently utilizing these attributes in your automation or scripts,
you’ll must adapt them to this transformation.
(@jetpacktuxedo – #72658) (documentation)
Vesync switches that help power monitoring can have their:
- Voltage attribute moved from the change entity to a devoted Voltage Sensor
entity - Weekly, month-to-month and yearly moved from the change entity attributes into new
power sensors.
When you used these entity attributes in your automation or scripts, you’d want
to adapt them to this transformation.
(@b3nj1 – #72570) (documentation)
With this launch, you will want to replace your zwave-js-server occasion.
- When you use the zwave_js add-on, you want no less than model
0.1.64. - When you use the Z-Wave JS 2 MQTT add-on, you want no less than model
0.44.0. - When you use the zwavejs2mqtt Docker container, you want no less than model
6.13.0. - When you run your personal Docker container or another set up methodology,
you will want to replace your zwave-js-server occasion to no less than1.20.0.
(@raman325 – #73707 #73904) (documentation)
If you’re a customized integration developer and need to study breaking
adjustments and new options accessible on your integration: Make sure to comply with our
developer weblog. The next are essentially the most notable for this launch:
Farewell to the next
The next integrations are additionally now not accessible as of this launch:
- iAlarm XR has been eliminated on request by Antifurto365 (producer).
-
Somfy has been beforehand deprecated and now eliminated. Its cloud API was
shut down on June twenty first, 2022. Use the Overkiz integration
as a substitute.
All adjustments
After all, there’s much more on this launch. You’ll find an inventory of
all adjustments made right here: Full changelog for House Assistant Core 2022.7
