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 Year of the Voice. 🎙️
It’s onerous to sum up all of this on this launch weblog, so I’m not even going
to strive doing it on this introduction, however holy mom of good houses: that is
thrilling stuff! 😮

My private favourite this launch: enormous steps into a good tighter integration
with our wonderful sister undertaking: ESPHome. Creating
and sustaining your personal safe DIY IoT gadgets simply turned lots 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 arising. You’ll want to share the love! ❤️

• Meet: Assist!
• Streaming history
• Grouping sensors
• Now even tighter integrated with ESPHome
• Other noteworthy changes
• New Integrations
• Integrations now available to set up from the UI
• Release 2023.2.1 – February 2
• Need help? Join the community!
• Breaking Changes
• Farewell to the following
• All changes

Don’t overlook to join our release party live stream on YouTube 1 February 2023, at 12:00 PST / 21:00 CET!

Meet: Help!

It’s Home Assistant’s Year of the Voice, and
it’s our purpose to let customers management House Assistant in their very own language.
Along with the House Assistant neighborhood, we have now been onerous at work constructing
the inspiration for this.

At this time we such as you to fulfill:

Help
means that you can use pure language to manage House Assistant. It’s powered by
Hassil and the sentences
(contributed by 112! folks) from the
Home Assistant Intents undertaking.

We imagine know-how is supposed to be performed with, and initiatives needs to be
usable as quickly as potential. Along with the neighborhood, we are able to then iterate
and refine. That’s why in the present day, we’re delivering a fundamental expertise supporting
a shocking 22! languages that work with Help.

Go forward, it’s enabled by default; simply faucet the brand new Help icon

on the prime proper of your dashboard to start out utilizing it.

Oh, and we’re additionally releasing some enjoyable stuff we’ve cooked up alongside the best way!
Read more about Assist and different launched voice options within the
Chapter 1: Assist blogpost
and a video presentation (including live demos) on YouTube.

Streaming historical past

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

These historical past playing cards now present dwell energy utilization, whereas I am brewing a cup of espresso.

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

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

As a side-effect, it also needs to resolve the authentication errors some folks
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,
number, and number helpers
entities.

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 seemingly we’re going to change these with this new sensor group
sooner or later.

In comparison with these beforehand talked about strategies, the sensor teams have the
extra choices to cover their member entities and the choice to disregard
sensors that presently aren’t in a numeric state (i.e., presently “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 have now some nice enhancements for you.
The add-on and House Assistant will now talk with one another, bringing
in lots of new options.

While you arrange a brand new gadget in ESPHome and subsequent add it to House Assistant,
they are going to have the ability 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 isn’t all. What is basically mind-blowing, is that the ESPHome
integration will now present replace entities when utilizing the add-on!

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 should help updating them too! Sure, at that time, you possibly can replace your
ESPHome gadgets instantly 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 certainly one of your ESPHome gadgets
remains to be utilizing a plain password, House Assistant will notify you by creating
a difficulty in your Repairs dashboard.

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

Different noteworthy adjustments

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

• Now you can add aliases to your areas too! Our new Help characteristic
  leverages this.
• Received an vitality sensor in Wh, however you’d prefer it to be kWh? Now you can
  change the models of vitality sensors within the entity settings.
• Every entity within the frontend has its personal shade, which relies on the present
  entity state. We now have officially added support
  for themes to customise these.
• Essentially the most superior integration of all, obtained even higher. @Lash-L added help
  for the battery state of your Oral-B toothbrush!
• The automations & scripts UI now help deciding on different entities for
  above/under within the numeric state situations & triggers. Thanks, @karwosts!
• The Reolink integration now helps FLV streams, cameras may be found
  on the community, however extra importantly: binary sensors! For issues
  like movement, particular person, car 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! Superb, @allenporter!
• When deciding on a number of entities from a listing within the UI, it should now exclude
  already added entities. No extra by accident added duplicates! Thanks, @piitaya!
• @Kane610 added PoE energy sensors to the UniFi Network 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!
• Now we have bumped the CHIP/Matter SDK model utilized by our Matter implementation
  to 1.0.0.2, which contains many fixes.
• From the Month of “What the heck?”: Previous-style groups 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 presently 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 one radio present in each House Assistant
  Yellow and House Assistant SkyConnect.
• The next integrations now reached a Platinum degree on the
  integration quality scale:
  • Renault wonderful job @epenet!
  • HomeWizard Energy superior work @DCSBL!

New Integrations

We welcome the next new integrations on this launch:

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

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

• Everything but the Kitchen Sink, added by @emontnemery
  It is 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 companies 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 together with your Mopeka BLE propane tank displays.

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

• Read Your Meter Pro, 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 Box, added by @epenet
  Affords 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 may forestall well being issues for folks within the space
  (NL solely).

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

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:

• ANWB Energie supplied by EnergyZero, added by @klaasnicolaas
• Energie VanOns supplied by EnergyZero, added by @klaasnicolaas
• Mijndomein Energie supplied by EnergyZero, added by @klaasnicolaas
• Fire TV supplied by Android TV, added by @jrieger

Integrations now out there to arrange from the UI

The next integrations at the moment are out there by way of the House Assistant UI:

• Rain Bird, finished by @allenporter
• IMAP, finished by @engrbm87
• D-Link, finished by @tkdrob

Launch 2023.2.1 – February 2

• Help ISY994 Z-Wave motorized blinds as cowl (@shbatm – #87102) (isy994 docs)
• Bump reolink_aio to 0.3.1 (@starkillerOG – #87118) (reolink docs)
• Bump reolink-aio to 0.3.2 (@starkillerOG – #87121) (reolink docs)
• Repair invalid state class in renault (@epenet – #87135) (renault docs)
• Add lacking converters to recorder statistics (@epenet – #87137) (recorder docs)
• Add lacking supported options to Z-Wave.Me siren (@lawfulchaos – #87141) (zwave_me docs)
• Reolink unsubscribe webhook when first refresh fails (@starkillerOG – #87147) (reolink docs)
• Repair statistics graphs not loading with data_rate, electric_current, voltage, info, and unitless models (@bdraco – #87202) (recorder docs)
• Add Reauth config circulate to honeywell (@mkmer – #86170) (honeywell docs)
• Bump AIOSomecomfort to 0.0.6 (@mkmer – #87203) (honeywell docs)
• Replace frontend to 20230202.0 (@bramkragten – #87208) (frontend docs)
• Bump py-synologydsm-api to 2.1.1 (@mib1185 – #87211) (synology_dsm docs)
• Repair disabled situation inside an automation motion (@karliemeads – #87213) (breaking-change)

Need assistance? Be part of the neighborhood!

House Assistant has an amazing neighborhood of customers who’re all greater than keen
to assist one another out. So, be part of us!

Our very lively Discord chat server is a wonderful place to be
at, and don’t overlook to affix our wonderful forums.

Discovered a bug or problem? Please report it in our issue tracker,
to get it mounted! Or, examine our help page for steering for extra
locations you possibly can go.

Are you extra into electronic mail? Sign-up for our Building the Open Home Newsletter
to get the newest information about options, issues taking place 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;

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;

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;

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;

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;

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;

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;

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;

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;

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;

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;

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;

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;

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;

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;

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;

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;

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;

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;

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;

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;

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;

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;

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;

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;

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 a customized integration developer and need to find out about breaking
adjustments and new options out there in your integration: You’ll want to comply with our
developer blog. The next are essentially the most notable for this launch:

• Bluetooth updates for 2023.2 and later
• Cover intents deprecated
• Database schema v32 updates
• Future proofing the Conversation integration
• Sensor entity can now do rounding of numerical values

Farewell to the next

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

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

All adjustments

After all, there’s much more on this launch. You could find a listing of
all adjustments made right here: Full changelog for Home Assistant Core 2023.2