2023.2: How can I Help?


House Assistant Core 2023.2! 🎉

This launch covers the primary month of growth of 2023, and it’s setting
one heck of a excessive bar for the remainder of the 12 months! 😅

Undoubtedly, essentially the most spectacular options are associated to the
first chapter of Yr of the Voice. 🎙️
It’s laborious to sum up all of this on this launch weblog, so I’m not even going
to attempt doing it on this introduction, however holy mom of sensible houses: that is
thrilling stuff! 😮

My private favourite this launch: enormous steps into an excellent tighter integration
with our superb sister challenge: ESPHome. Creating
and sustaining your personal safe DIY IoT units simply grew to become loads simpler.

And since we’re speaking about awesomeness, have you ever seen the big quantity
of logos within the launch picture above? So many new integrations! 🤩

Benefit from the launch!

../Frenck

PS: Only a reminder that valentine’s day is developing. Be sure you share the love! ❤️

Don’t overlook to be a part of our launch get together reside stream on YouTube 1 February 2023, at 12:00 PST / 21:00 CET!

Meet: Help!

It’s House Assistant’s Yr of the Voice, and
it’s our objective to let customers management House Assistant in their very own language.
Along with the House Assistant neighborhood, we’ve been laborious at work constructing
the inspiration for this.

At this time we such as you to satisfy:

Screenshot showing the new assist feature being used to turn on lights

Assist icon Help
means that you can use pure language to regulate House Assistant. It’s powered by
Hassil and the sentences
(contributed by 112! individuals) from the
House Assistant Intents challenge.

We imagine know-how is supposed to be performed with, and tasks ought to be
usable as quickly as potential. Along with the neighborhood, we will then iterate
and refine. That’s why right this moment, we’re delivering a primary expertise supporting
a shocking 22! languages that work with Help.

Go forward, it’s enabled by default; simply faucet the brand new Help icon
Assist icon
on the high proper of your dashboard to begin utilizing it.

Oh, and we’re additionally releasing some enjoyable stuff we’ve cooked up alongside the best way!
Learn extra about Help and different launched voice options within the
Chapter 1: Help blogpost
and a video presentation (together with reside demos) on YouTube.

Streaming historical past

Historical past playing cards now replace reside! We now stream the state adjustments whereas they’re
occurring and replace the graphs in real-time 😲

Screenshot showing a history card presenting the power usage of a kitchen coffeemaker, updating live while brewing coffee
These historical past playing cards now present reside energy utilization, whereas I am brewing a cup of espresso.

However this isn’t simply restricted to historical past playing cards, your
historical past dashboard is now reside too!

On account of this all, we will now write much less often to the database in our
recorder. It took years of adjustments to get us thus far (thanks @bdraco 🙏).
It significantly reduces useful resource utilization and will increase storage lifetimes considerably.
The beforehand launched reside logbook and now the reside historical past had been the
final items that made this potential.

As a side-effect, it must also resolve the authentication errors some individuals
skilled re-opening the iOS companion app when utilizing historical past playing cards.

Grouping sensors

The group helper now helps sensors too! Sensor teams
can mix entities with a numeric state, like sensors,
quantity, and quantity helpers
entities.

Screenshot showing the process of adding a new sensor group

This characteristic is a revised, improved, and extra logical model of the
“Min/Max” integration / “Mix the state of a number of sensors” helper.
It’s doubtless we’re going to substitute these with this new sensor group
sooner or later.

In comparison with these beforehand talked about strategies, the sensor teams have the
further choices to cover their member entities and the choice to disregard
sensors that at present aren’t in a numeric state (i.e., at present “unavailable”
or “unknown”).

Now even tighter built-in with ESPHome

ESPHome already works rather well with House Assistant.
But, this launch makes it even higher!

If you’re utilizing the ESPHome add-on, we’ve some nice enhancements for you.
The add-on and House Assistant will now talk with one another, bringing
in lots of new options.

Whenever you arrange a brand new machine in ESPHome and subsequent add it to House Assistant,
they may be capable to change encryption keys. Eradicating the necessity so that you can
discover, copy & paste these. Only a single click on and the setup is completed! 🚀

However that’s not all. What is de facto mind-blowing, is that the ESPHome
integration will now present replace entities when utilizing the add-on!

Screenshots, left one showing pending updates for ESPHome devices. Right one: an ESPHome device installing an update straight from Home Assistant

Proper now, the replace entities will solely point out if a tool wants updating.
Nonetheless, when the following main launch of ESPHome (2023.2) turns into out there,
it’ll assist updating them too! Sure, at that time, you possibly can replace your
ESPHome units straight from House Assistant and even automate it!

Additionally, ESPHome is deprecating the outdated password-based authentication for its
API in favor of the safer encryption key. If one among your ESPHome units
continues to be utilizing a plain password, House Assistant will notify you by creating
a problem in your Repairs dashboard.

Screenshot showing a raised repair issue for an ESPHome device still using the deprecated API password instead of an API encryption key

We’ve additionally ready for the following launch of ESPHome (2023.2), in which you’ll be able to
add a pleasant, extra human identify to your ESPHome units. House Assistant will
decide these up, making your ESPHome units look higher out-of-the-box!

Different noteworthy adjustments

There’s far more juice on this launch; listed below are among the different
noteworthy adjustments this launch:

  • Now you can add aliases to your areas too! Our new Help characteristic
    leverages this.
  • Acquired an vitality sensor in Wh, however you’d prefer it to be kWh? Now you can
    change the items of vitality sensors within the entity settings.
  • Every entity within the frontend has its personal colour, which is predicated on the present
    entity state. We now have formally added assist
    for themes to customise these.
  • Essentially the most superior integration of all, acquired even higher. @Lash-L added assist
    for the battery state of your Oral-B toothbrush!
  • The automations & scripts UI now assist deciding on different entities for
    above/under within the numeric state circumstances & triggers. Thanks, @karwosts!
  • The Reolink integration now helps FLV streams, cameras will be found
    on the community, however extra importantly: binary sensors! For issues
    like movement, particular person, automobile detection, and… Doorbell presses!
    Thanks, @starkillerOG!
  • There’s now a service that permits for the creation of calendar occasions. So,
    now you can automate occasions to be added to your calendars! Wonderful, @allenporter!
  • When deciding on a number of entities from an inventory within the UI, it’ll now exclude
    already added entities. No extra by chance added duplicates! Thanks, @piitaya!
  • @Kane610 added PoE energy sensors to the UniFi Community integrations, good!
  • The Tile card now has a vertical possibility! Nice, @TheZoker!
  • Jellyfin now works with TV reveals within the media browser. Thanks, @j-stienstra!
  • We’ve got bumped the CHIP/Matter SDK model utilized by our Matter implementation
    to 1.0.0.2, which incorporates many fixes.
  • From the Month of “What the heck?”: Outdated-style teams can now take away entities
    from the group utilizing the group.set service. Thanks, @gjohansson-ST!
  • You may need seen a Thread and an Open Thread Border Router integration
    being added to this launch. These are at present not for lively use however for
    preliminary early growth.
  • The experimental multi-pan characteristic has been enabled once more. Permitting to run
    each Zigbee and Thread utilizing the only radio present in each House Assistant
    Yellow and House Assistant SkyConnect.
  • The next integrations now reached a Platinum stage on the
    integration high quality scale:

New Integrations

We welcome the next new integrations on this launch:

  • EnergyZero, added by @klaasnicolaas
    Retrieves dynamic (hourly) vitality & fuel costs from the Dutch utility firm
    EnergyZero.

  • EufyLife, added by @bdr99
    Combine Eufy sensible scales over Bluetooth.

  • All the things however the Kitchen Sink, added by @emontnemery
    This can be a take a look at integration, which supplies numerous odd and obscure entities.
    It may be useful for growth functions, however typically no use in any other case.

  • Google Mail, added by @tkdrob
    Offers providers to handle your Google Mail auto-response and supplies
    a notification service to ship (or draft) emails.

  • LD2410 BLE, added by @930913
    Integrates a $4 LD2410 Bluetooth mmWave sensor, which works with our
    Bluetooth proxies!

  • Mopeka, added by @bdraco
    Works along with your Mopeka BLE propane tank displays.

  • OpenAI Dialog, added by @balloob
    OpenAI integration that makes use of GPT-3 to showcase changing the House Assistant
    dialog agent. Be aware: It can’t management something in your house.

  • Learn Your Meter Professional, added by @OnFreund
    Pull in your water utilization/meter readings out of your Learn Your Meter Professional account.

  • Ruuvi Gateway, added by @akx
    Integrates the Ruuvi Gateway that reads your Ruuvi sensors.

  • SFR Field, added by @epenet
    Presents integration with the SFR broadband routers.

  • Starlink, added by @boswelja
    Starlink is a satellite tv for pc web constellation operated by SpaceX.
    Combine your Starlink dish with House Assistant.

  • Stookwijzer, added by @fwestenberg
    Stookwijzer advises wether to burn pallets or wooden, or to
    use the barbecue. This will stop well being issues for individuals within the space
    (NL solely).

  • Zeversolar, added by @kvanzuijlen
    Get energy and vitality data out of your Zeversolar photo voltaic inverter domestically.

This launch additionally has some new digital integrations. Digital integrations
are stubs which might be dealt with by different (present) integrations to assist with
findability. These are new:

Integrations now out there to arrange from the UI

The next integrations are actually out there through the House Assistant UI:

Launch 2023.2.1 – February 2

Launch 2023.2.2 – February 4

Launch 2023.2.3 – February 7

Launch 2023.2.4 – February 13

Launch 2023.2.5 – February 15

Need assistance? Be a part of the neighborhood!

House Assistant has an excellent neighborhood 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 possibly can go.

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

Breaking Modifications

perform showDetails(el) {
const content material = el.parentElement.querySelector(“.details-block-content”);
const up = el.querySelector(“svg#up”);
const down = el.querySelector(“svg#down”);
const shouldExpand = down.type.show === “block”;
up.type.show = shouldExpand ? “block” : “none”;
down.type.show = !shouldExpand ? “block” : “none”;
content material.hidden = !shouldExpand;
el.ariaExpanded = shouldExpand;
}

Python 3.9 assist has beforehand been deprecated and has now been eliminated.
House Assistant now requires Python 3.10 to run.

If you’re utilizing House Assistant OS, House Assistant Container, or House Assistant
Supervised set up methodology, you don’t must do something. In these instances,
we deal with this all for you.

Your system has been utilizing Python 3.10 for fairly a while already.

(@frenck#85456)

perform showDetails(el) {
const content material = el.parentElement.querySelector(“.details-block-content”);
const up = el.querySelector(“svg#up”);
const down = el.querySelector(“svg#down”);
const shouldExpand = down.type.show === “block”;
up.type.show = shouldExpand ? “block” : “none”;
down.type.show = !shouldExpand ? “block” : “none”;
content material.hidden = !shouldExpand;
el.ariaExpanded = shouldExpand;
}

If you’re utilizing MariaDB with House Assistant recorder, please be certain
you run 10.5.17 , 10.6.9, 10.7.5, 10.8.4 (relying on which main
launch you might be utilizing). If you’re utilizing the MariaDB core add-on,
be certain to replace it to the newest model: 2.5.2.

Older variations of MariaDB endure from a major efficiency regression
when retrieving historical past knowledge or purging the database.

(@bdraco#87040)

perform showDetails(el) {
const content material = el.parentElement.querySelector(“.details-block-content”);
const up = el.querySelector(“svg#up”);
const down = el.querySelector(“svg#down”);
const shouldExpand = down.type.show === “block”;
up.type.show = shouldExpand ? “block” : “none”;
down.type.show = !shouldExpand ? “block” : “none”;
content material.hidden = !shouldExpand;
el.ariaExpanded = shouldExpand;
}

A disabled situation, for instance, in an automation or script, will now not
all the time be a move/True inside an OR situation. As a substitute, in these
instances, the situation will now haven’t any impact when disabled.

(@karliemeads#79718) (documentation)

perform showDetails(el) {
const content material = el.parentElement.querySelector(“.details-block-content”);
const up = el.querySelector(“svg#up”);
const down = el.querySelector(“svg#down”);
const shouldExpand = down.type.show === “block”;
up.type.show = shouldExpand ? “block” : “none”;
down.type.show = !shouldExpand ? “block” : “none”;
content material.hidden = !shouldExpand;
el.ariaExpanded = shouldExpand;
}

For the precipitation entity, the unit was modified from mm to mm/h
(in to in/h), leading to the necessity to repair the unit for long-term
statistics. You are able to do that in Developer Instruments -> Stats.

(@bieniu#86088) (documentation)

perform showDetails(el) {
const content material = el.parentElement.querySelector(“.details-block-content”);
const up = el.querySelector(“svg#up”);
const down = el.querySelector(“svg#down”);
const shouldExpand = down.type.show === “block”;
up.type.show = shouldExpand ? “block” : “none”;
down.type.show = !shouldExpand ? “block” : “none”;
content material.hidden = !shouldExpand;
el.ariaExpanded = shouldExpand;
}

If the language within the House Assistant settings is ready to Polish, the language
of the recommendation and description attributes of the CAQI entity will change
from English to Polish.

If you’re utilizing these in your automations or scripts, you would possibly want to regulate
them to match this modification.

(@bieniu#85655) (documentation)

perform showDetails(el) {
const content material = el.parentElement.querySelector(“.details-block-content”);
const up = el.querySelector(“svg#up”);
const down = el.querySelector(“svg#down”);
const shouldExpand = down.type.show === “block”;
up.type.show = shouldExpand ? “block” : “none”;
down.type.show = !shouldExpand ? “block” : “none”;
content material.hidden = !shouldExpand;
el.ariaExpanded = shouldExpand;
}

The state values of the Fitbit sensor entities will change to take away any
1000’s delimiters. For instance, 1,500 will change into 1500.

For those who’re utilizing the state of those entities in automations or scripts,
it’s essential replace them to deal with the brand new state format.

(@sw-carlos-cristobal#85251) (documentation)

perform showDetails(el) {
const content material = el.parentElement.querySelector(“.details-block-content”);
const up = el.querySelector(“svg#up”);
const down = el.querySelector(“svg#down”);
const shouldExpand = down.type.show === “block”;
up.type.show = shouldExpand ? “block” : “none”;
down.type.show = !shouldExpand ? “block” : “none”;
content material.hidden = !shouldExpand;
el.ariaExpanded = shouldExpand;
}

The scan/replace interval for water values has been restored to match the Flume
app.

To remain underneath Flume’s API limits, the machine connection is now checked hourly,
and notifications are checked each 5 minutes.

(@bdraco#86354) (documentation)

perform showDetails(el) {
const content material = el.parentElement.querySelector(“.details-block-content”);
const up = el.querySelector(“svg#up”);
const down = el.querySelector(“svg#down”);
const shouldExpand = down.type.show === “block”;
up.type.show = shouldExpand ? “block” : “none”;
down.type.show = !shouldExpand ? “block” : “none”;
content material.hidden = !shouldExpand;
el.ariaExpanded = shouldExpand;
}

The use_include_order YAML configuration possibility has been eliminated.

This selection was used to type the historical past on the unique historical past panel which,
is now not used. Because it now not has a perform and solely serves to
decelerate the response, it has been eliminated.

(@bdraco#86365) (documentation)

perform showDetails(el) {
const content material = el.parentElement.querySelector(“.details-block-content”);
const up = el.querySelector(“svg#up”);
const down = el.querySelector(“svg#down”);
const shouldExpand = down.type.show === “block”;
up.type.show = shouldExpand ? “block” : “none”;
down.type.show = !shouldExpand ? “block” : “none”;
content material.hidden = !shouldExpand;
el.ariaExpanded = shouldExpand;
}

The IoTAWatt integration now not supplies sensors with the “Accrued”
suffix. The collected sensors have been launched to assist internet vitality
export/import metering.

Newer variations of IoTaWatt present “Integrators”, which permit attaining the
similar extra effectively and with larger accuracy.

It’s best to configure Integrators
to calculate the web vitality export and import.

(@agners#86611) (documentation)

perform showDetails(el) {
const content material = el.parentElement.querySelector(“.details-block-content”);
const up = el.querySelector(“svg#up”);
const down = el.querySelector(“svg#down”);
const shouldExpand = down.type.show === “block”;
up.type.show = shouldExpand ? “block” : “none”;
down.type.show = !shouldExpand ? “block” : “none”;
content material.hidden = !shouldExpand;
el.ariaExpanded = shouldExpand;
}

The Matter integration now requires working Matter Server model 2.0.0.

For those who’re utilizing the Matter Server add-on to run the Matter Server,
you will have model 3.0.0 of the add-on.

We needed to change our vendor ID within the add-on; in consequence, all units
have to be recommissioned.

(@MartinHjelmare#86470) (documentation)

perform showDetails(el) {
const content material = el.parentElement.querySelector(“.details-block-content”);
const up = el.querySelector(“svg#up”);
const down = el.querySelector(“svg#down”);
const shouldExpand = down.type.show === “block”;
up.type.show = shouldExpand ? “block” : “none”;
down.type.show = !shouldExpand ? “block” : “none”;
content material.hidden = !shouldExpand;
el.ariaExpanded = shouldExpand;
}

The states of air high quality sensors have been standardized to match House Assistant
core guidelines. This impacts two states of the sensors that NAM can present:

  • very low, which now grew to become very_low
  • very excessive, which now grew to become very_high

For those who used these states straight in your automations, scripts, or templates;
you would want to regulate these to match these adjustments.

(@frenck#85245) (documentation)

perform showDetails(el) {
const content material = el.parentElement.querySelector(“.details-block-content”);
const up = el.querySelector(“svg#up”);
const down = el.querySelector(“svg#down”);
const shouldExpand = down.type.show === “block”;
up.type.show = shouldExpand ? “block” : “none”;
down.type.show = !shouldExpand ? “block” : “none”;
content material.hidden = !shouldExpand;
el.ariaExpanded = shouldExpand;
}

The Pentair ScreenLogic integration now appropriately categorizes all recognized lights.
Eradicating any lights that had been beforehand incorrectly created as change entities
could also be mandatory.

(@dieselrabbit#86608) (documentation)

perform showDetails(el) {
const content material = el.parentElement.querySelector(“.details-block-content”);
const up = el.querySelector(“svg#up”);
const down = el.querySelector(“svg#down”);
const shouldExpand = down.type.show === “block”;
up.type.show = shouldExpand ? “block” : “none”;
down.type.show = !shouldExpand ? “block” : “none”;
content material.hidden = !shouldExpand;
el.ariaExpanded = shouldExpand;
}

The beforehand deprecated YAML configuration of the Pi-hole
integration has been eliminated.

Pi-hole is now configured through the UI. Any present YAML configuration
has been imported in earlier releases and may now be safely eliminated out of your
YAML configuration recordsdata.

(@mib1185#84803) (documentation)


The additional state attribute “Domains blocked” has been faraway from all sensors.
It’s already uncovered as its personal devoted sensor.

For those who used the state attribute in your automations or scripts, you’ll
want to regulate them to make use of the devoted sensor as a substitute.

(@mib1185#85424) (documentation)

perform showDetails(el) {
const content material = el.parentElement.querySelector(“.details-block-content”);
const up = el.querySelector(“svg#up”);
const down = el.querySelector(“svg#down”);
const shouldExpand = down.type.show === “block”;
up.type.show = shouldExpand ? “block” : “none”;
down.type.show = !shouldExpand ? “block” : “none”;
content material.hidden = !shouldExpand;
el.ariaExpanded = shouldExpand;
}

Rainbird is now configured through the UI, and configuration from YAML has been
imported robotically.

Nonetheless, there are a couple of notable adjustments:

  • Customized per zone overrides for irrigation time are now not supported.
  • The Rain delay binary_sensor that duplicates the Rain delay time sensor
    has been eliminated. It’s best to transfer all makes use of to the sensor worth and examine
    for a non-zero worth to get equal conduct.
  • The Rain sensor that duplicates the Rain binary_sensor has been eliminated.
    You might examine the binary_sensor state to get equal conduct.

Additionally, the best way the “Rain Delay” is managed has modified. The Rain Delay, which
pauses irrigation for a specified variety of days, is now managed with a quantity
entity which will be managed straight from the UI.

The prevailing service name rainbird.set_rain_delay and the Raindelay sensor
have been deprecated. Any present automations or scripts that make service
calls to rainbird.set_rain_delay will have to be changed with a name
to quantity.set_value. Moreover, the present service name was up to date to
require an integration entry configuration because it beforehand had undefined
conduct, so it is strongly recommended to maneuver on to the brand new quantity service name.

(@allenporter#85271 #86208) (documentation)

perform showDetails(el) {
const content material = el.parentElement.querySelector(“.details-block-content”);
const up = el.querySelector(“svg#up”);
const down = el.querySelector(“svg#down”);
const shouldExpand = down.type.show === “block”;
up.type.show = shouldExpand ? “block” : “none”;
down.type.show = !shouldExpand ? “block” : “none”;
content material.hidden = !shouldExpand;
el.ariaExpanded = shouldExpand;
}

The recorder’s default commit interval has been elevated to five seconds to
cut back disk I/O and improve storage longevity.

Because the historical past and logbook integrations each assist reside streaming, which
avoids the necessity to learn the database after the preliminary sync, there isn’t any
remaining core performance that wants a decrease commit interval.

The commit_interval will be adjusted
to a decrease worth within the occasion an integration has not been up to date to look at for
occasions as a substitute of studying the database and must learn the database sooner.

(@bdraco#86115) (documentation)

perform showDetails(el) {
const content material = el.parentElement.querySelector(“.details-block-content”);
const up = el.querySelector(“svg#up”);
const down = el.querySelector(“svg#down”);
const shouldExpand = down.type.show === “block”;
up.type.show = shouldExpand ? “block” : “none”;
down.type.show = !shouldExpand ? “block” : “none”;
content material.hidden = !shouldExpand;
el.ariaExpanded = shouldExpand;
}

The beforehand deprecated renault.charge_start service has been eliminated.
Please use the devoted begin cost button entity to begin the cost as a substitute.

(@epenet#86070) (documentation)

perform showDetails(el) {
const content material = el.parentElement.querySelector(“.details-block-content”);
const up = el.querySelector(“svg#up”);
const down = el.querySelector(“svg#down”);
const shouldExpand = down.type.show === “block”;
up.type.show = shouldExpand ? “block” : “none”;
down.type.show = !shouldExpand ? “block” : “none”;
content material.hidden = !shouldExpand;
el.ariaExpanded = shouldExpand;
}

Sony Bravia TV media gamers now not have faux (assumed) taking part in or paused
states, and people are changed with the on state.

In case you have automations or scripts that use the taking part in or paused state,
please replace them to be suitable with this modification.

(@Drafteed#84885) (documentation)


The source_list now not incorporates an inventory of purposes and TV channels.
Apps and channels have been separated from the enter checklist and moved
to the Media Browser.

In case you have automations or scripts that use media_player.select_source to
change apps or channels on the Bravia TV, the automations have to be
up to date to make use of media_player.play_media service as a substitute.

The choices circulate has been faraway from the mixing, as the one
configurable setting ignored_sources was now not related
and incompatible with this modification.

(@Drafteed#85288) (documentation)

perform showDetails(el) {
const content material = el.parentElement.querySelector(“.details-block-content”);
const up = el.querySelector(“svg#up”);
const down = el.querySelector(“svg#down”);
const shouldExpand = down.type.show === “block”;
up.type.show = shouldExpand ? “block” : “none”;
down.type.show = !shouldExpand ? “block” : “none”;
content material.hidden = !shouldExpand;
el.ariaExpanded = shouldExpand;
}

The beforehand deprecated YAML configuration of the Spain electrical energy hourly
pricing (PVPC) integration has been eliminated.

Spain electrical energy hourly pricing (PVPC) is now configured through the UI. Any
present YAML configuration has been imported in earlier releases and may now
be safely eliminated out of your YAML configuration recordsdata.

(@azogue#85614) (documentation)

perform showDetails(el) {
const content material = el.parentElement.querySelector(“.details-block-content”);
const up = el.querySelector(“svg#up”);
const down = el.querySelector(“svg#down”);
const shouldExpand = down.type.show === “block”;
up.type.show = shouldExpand ? “block” : “none”;
down.type.show = !shouldExpand ? “block” : “none”;
content material.hidden = !shouldExpand;
el.ariaExpanded = shouldExpand;
}

The swing modes of Tado have modified. That is to standardize with different
integrations, and so it could possibly assist translations.

  • ON grew to become the lowercase on
  • OFF grew to become the lowercase off

For those who used these swing modes in your automations or scripts, you would possibly
want to regulate these to this modification.

(@emontnemery#84278) (documentation)

perform showDetails(el) {
const content material = el.parentElement.querySelector(“.details-block-content”);
const up = el.querySelector(“svg#up”);
const down = el.querySelector(“svg#down”);
const shouldExpand = down.type.show === “block”;
up.type.show = shouldExpand ? “block” : “none”;
down.type.show = !shouldExpand ? “block” : “none”;
content material.hidden = !shouldExpand;
el.ariaExpanded = shouldExpand;
}

All additional state attributes from Twinkly gentle entities have been eliminated.

They principally added details about the machine,
not the precise gentle state itself.

(@frenck#84986) (documentation)

perform showDetails(el) {
const content material = el.parentElement.querySelector(“.details-block-content”);
const up = el.querySelector(“svg#up”);
const down = el.querySelector(“svg#down”);
const shouldExpand = down.type.show === “block”;
up.type.show = shouldExpand ? “block” : “none”;
down.type.show = !shouldExpand ? “block” : “none”;
content material.hidden = !shouldExpand;
el.ariaExpanded = shouldExpand;
}

ISY/IoX Variables have been moved from sensor entities to quantity entities;
the present sensor entities are deprecated and might be eliminated in a future
launch.

The isy994.set_variable service has been deprecated in favor of utilizing
the quantity entities to straight set the variable values.

Please replace any dashboards, scripts, and automations which may be utilizing these
entities or service.

(@shbatm#85511) (documentation)


Entities for INSTEON Aux Properties and Gadget Communication Errors have been
eliminated for nodes that aren’t the principle (load) node.

On Stage and Ramp Charge sensors have been eliminated for non-dimmable (non-gentle.)
units. Solely load units obtain communication error updates and solely
dimmable units assist OL and RR instructions.

The opposite entities had been beforehand added however didn’t obtain legitimate states from
the ISY or end-devices. These sensors had been disabled by default.

(@shbatm#85744) (documentation)

perform showDetails(el) {
const content material = el.parentElement.querySelector(“.details-block-content”);
const up = el.querySelector(“svg#up”);
const down = el.querySelector(“svg#down”);
const shouldExpand = down.type.show === “block”;
up.type.show = shouldExpand ? “block” : “none”;
down.type.show = !shouldExpand ? “block” : “none”;
content material.hidden = !shouldExpand;
el.ariaExpanded = shouldExpand;
}

The beforehand deprecated YAML configuration of the Uptime
integration has been eliminated.

Uptime is now configured through the UI. Any present YAML configuration has been
imported in earlier releases and may now be safely eliminated out of your YAML
configuration recordsdata.

(@frenck#86292) (documentation)

perform showDetails(el) {
const content material = el.parentElement.querySelector(“.details-block-content”);
const up = el.querySelector(“svg#up”);
const down = el.querySelector(“svg#down”);
const shouldExpand = down.type.show === “block”;
up.type.show = shouldExpand ? “block” : “none”;
down.type.show = !shouldExpand ? “block” : “none”;
content material.hidden = !shouldExpand;
el.ariaExpanded = shouldExpand;
}

When there’s a connection error with the receiver, the machine will now
go into an unavailable state till the connection has been restored.

(@sredna#85018) (documentation)

perform showDetails(el) {
const content material = el.parentElement.querySelector(“.details-block-content”);
const up = el.querySelector(“svg#up”);
const down = el.querySelector(“svg#down”);
const shouldExpand = down.type.show === “block”;
up.type.show = shouldExpand ? “block” : “none”;
down.type.show = !shouldExpand ? “block” : “none”;
content material.hidden = !shouldExpand;
el.ariaExpanded = shouldExpand;
}

The uncooked state/possibility values of the Yamaha MusicCast zone sleep choose entities
have been standardized to match House Assistant core guidelines.

The next states/choices have been modified

  • 120 min, which now grew to become 120_min
  • 90 min, which now grew to become 90_min
  • 60 min, which now grew to become 60_min
  • 30 min, which now grew to become 30_min

For those who used these states/choices straight in your automations, scripts,
or templates; you will have to regulate these to match these adjustments.

(@frenck#85292) (documentation)

perform showDetails(el) {
const content material = el.parentElement.querySelector(“.details-block-content”);
const up = el.querySelector(“svg#up”);
const down = el.querySelector(“svg#down”);
const shouldExpand = down.type.show === “block”;
up.type.show = shouldExpand ? “block” : “none”;
down.type.show = !shouldExpand ? “block” : “none”;
content material.hidden = !shouldExpand;
el.ariaExpanded = shouldExpand;
}

The beforehand deprecated YAML configuration of the Zentralanstalt für
Meteorologie und Geodynamik (ZAMG) integration has been eliminated.

Zentralanstalt für Meteorologie und Geodynamik (ZAMG) is now configured through the
UI. Any present YAML configuration has been imported in earlier releases and
can now be safely eliminated out of your YAML configuration recordsdata.

(@killer0071234#86113) (documentation)

perform showDetails(el) {
const content material = el.parentElement.querySelector(“.details-block-content”);
const up = el.querySelector(“svg#up”);
const down = el.querySelector(“svg#down”);
const shouldExpand = down.type.show === “block”;
up.type.show = shouldExpand ? “block” : “none”;
down.type.show = !shouldExpand ? “block” : “none”;
content material.hidden = !shouldExpand;
el.ariaExpanded = shouldExpand;
}

The AnalogInput sensor entities for sure Xiaomi plugs have been eliminated
from ZHA.

Correctly working “Lively energy” and “Summation delivered” sensors can be found
to switch the older entities. These newer sensor entities can be utilized in
House Assistant Power dashboard.

(@TheJulianJES#86261) (documentation)

If you’re a customized integration developer and wish to study breaking
adjustments and new options out there on your integration: Be sure you observe our
developer weblog. The next are essentially the most notable for this launch:

Farewell to the next

The next integrations are additionally now not out there as of this launch:

  • Almond has been eliminated. It’s in a non-working state, and the providers
    have been shut down.
  • OpenALPR Native was beforehand deprecated and has now been eliminated. It
    doesn’t work appropriately and has no utilization, in line with our public analytics.

All adjustments

In fact, there may be much more on this launch. Yow will discover an inventory of
all adjustments made right here: Full changelog for House Assistant Core 2023.2

Leave a Reply

Your email address will not be published. Required fields are marked *