2022.12: It does matter! – Dwelling Assistant
Dwelling Assistant Core 2022.12! 🎄
Already the final launch of the yr, proper on time to carry you some cool
new options to work with through the upcoming Holidays!
2022 has been a implausible yr for the Dwelling Assistant mission. We turned
one of many world’s largest and fastest-growing GitHub open source projects! ❤️ Tons of latest options every month, and never simply that,
we matured so much! The whole lot turned extra steady and quicker, and
the UX made leaps forwards as nicely!
We regarded again at 2022 through the State of the Open Home,
and sneak peaked at 2023, with some nice new UI ideas
and: The yr of the voice! 🗣️ Missed it?
The full video is available on YouTube.
However! The yr isn’t over but! This launch actually Issues! We’re thrilled to
be one of many first on the planet to roll out Matter help to the general public! 🎉
No Matter gadgets but? Don’t fear! There are tons of issues on this launch
that can maintain you busy. The Tile card acquired “options”! Now you can prolong
your Bluetooth vary utilizing Shelly gadgets, and a long-requested function lands:
Native Calendar. 🤩
For 2022, that is it! Thanks for becoming a member of our neighborhood. Thanks for
sharing, serving to out, contributing, creating YouTube movies, weblog articles,
Thanks for utilizing Dwelling Assistant! ❤️
Completely satisfied holidays and for the final time in 2022: Benefit from the launch!
Don’t overlook to join our release party live stream on YouTube as we speak at 12:00 PDT / 21:00 CET!
It does Matter!
Does it Matter? Yes, Home Assistant does Matter!
Matter is a new smart home interoperability standard, an open-source protocol,
that defines how devices can communicate and work together. Read more about
Matter in this comprehensive write-up from The Verge.
Immediately we launch the primary iteration of the Matter integration for Dwelling
Assistant. It’s a massive and vital basis that’s most likely finest described
as “alpha” or perhaps even a “developer preview” — permitting anybody to assist
and soar in on the Matter improvement. For the primary launch,
we expect that may be a nice begin!
At this level, Matter-enabled merchandise should not (but) typically accessible.
Nonetheless, if you will get a Matter-certified product, it may be commissioned!
A Matter machine built-in with Dwelling Assistant.
Including Matter gadgets (commissioning) will be achieved utilizing our iOS and Android
Dwelling Assistant Companion apps. Including help for this to our apps is being
labored on and can grow to be accessible within the upcoming weeks. The Android Companion
app supporting Matter, is presently accessible for beta testing.
? We’ve made extra particulars accessible in our documentation.
Tile card will get options
Within the final launch, we introduced the Tile card.
Today we extend the Tile card by adding support for “features”.
For the Tile card, “features” are additional extras that can be added to a Tile
card. For example, they can provide additional controls or information for
the entity the Tile card displays.
Multiple usable Tile features have been added:
- Command buttons for vacuum cleaners
- Brightness slider for lights
- Controls for opening/closing and tilting covers
Checkout the documentation for more information about Tile features
But that is not all! The Tile card also got colors! 🎨
Based on the entity’s state, the card will get different colors. This color
provides an additional visual indication of the entity’s state.
Shiny new state colors!
Those lovely new state colors added to the Tile card, as shown above, are not
just added to the tile card. This same color logic has now also been applied to
the state history and the logbook!
Previously, these colors would be random. Now they are predictable, recognizable
and, above all: just look a lot better 🤩
This same experience will also be visible on the dedicated Logbook and History
pages of course.
This is one of the longer outstanding and bigger requested features
of Home Assistant: A local calendar!
Building a calendar isn’t easy, but Allen Porter did it! And it’s not
only a calendar with dates and descriptions… oh no! Allen went all in!
We now have a full blown, native, built-in calendar, which might do all-day occasion
or recurring ones tuned to your liking. Even a number of completely different native calendars
Bluetooth proxy utilizing Shelly gadgets
Within the September launch, we introduced Bluetooth everywhere,
by adding Bluetooth proxy support, allowing any ESPHome device in your home
to relay Bluetooth traffic across your home.
This release adds support for using Shelly devices as a remote Bluetooth
adapter as well!
It works with all second-generation Shelly devices that use firmware 12.0 or
later. Those are able to provide Bluetooth advertisements to Home Assistant’s
This can greatly help with extending the range of your Bluetooth network to
help with things like Bluetooth temperature or plant sensors in your home.
In other Bluetooth news: The performance of Bluetooth has, again, been improved
this release, and the memory usage should be lower. Always good!
New entity: text
Say hello to a new entity:
text! The text entity is very similar to the
Text helper (also known as
The difference is that the helper is configured and managed by you, while the
new text entities are provided by integrations. This means integration can now
provide entities that ask for a textual input in the UI.
The first integrations that can now provide text entities as of this release are
KNX and MQTT.
Summing entities without templates
Let’s say you have two numeric sensor entities, and you like to have an
entity that shows the sum of those two; how would you do that? Creating a
template entity, right? Nope! 😁
You can now create a new helper entity that sums the values of two (or more)
sensor entities into a brand-new entity.
When creating a new helper, select “Combine the state of several sensors”,
pick the sensor you’d like to sum, and select “Sum” for the statistic
You might need observed that this appears just like the “Min/Max” helper. True!
We’ve renamed “Min/Max” to “Mix the state of a number of sensors”,
to make it extra descriptive because it will get extra options.
Other noteworthy changes
There is much more juice in this release; here are some of the other
noteworthy changes this release:
- You can now set your country and default language Home Assistant should use
in the general settings. These new choices enable
Dwelling Assistant to think about these in future options.
- Utilizing Twinkly in your Christmas tree? 🎄 Now you can management the results!
Proper on time! Thanks, @Olen!
MQTT reached the gold stage on the mixing high quality scale! Good work @jbouwh!
However that’s not all; it now helps MQTT v5 and WebSocket connections too!
- NO2 and VOC sensor entities at the moment are working with HomeKit. Thanks, @stackia!
Shelly is now a platinum integration! Thanks, @thecode, @bieniu,
and @chemelli74 to your exhausting work on this integration 🥇
ZHA now helps the brand new Aqara c1 pet feeder. Thanks @dmulcahey for
including it, and thanks @kirovilya determining the communication!
- The humidifier card, now has on/off controls. Thanks, @Shulyaka
- Amazon Alexa now helps humidifiers. Thanks, @jbouwh!
BTHome model 2 has been launched and Dwelling Assistant now helps it!
- Slack now has a Do Not Disturb sensor you could possibly automate on. Thanks, @tkdrob!
- Help for IP-Safe routing has been added to KNX. Thanks, @farmio!
- Are you utilizing Picnic to your groceries? Now you can add merchandise to your
order straight from Dwelling Assistant. Thanks, @corneyl!
We welcome the next new integrations on this launch:
Integrations now available to set up from the UI
The following integrations are now available via the Home Assistant UI:
Release 2022.12.1 – December 8
Release 2022.12.2 – December 11
Release 2022.12.3 – December 11
Release 2022.12.4 – December 12
Release 2022.12.5 – December 13
Release 2022.12.6 – December 14
Release 2022.12.7 – December 17
Release 2022.12.8 – December 21
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 difficulty? Please report it in our issue tracker,
to get it fastened! Or, examine our assist web page for steerage for extra
locations you may go.
Are you extra into e mail? Signal-up for our Constructing the Open Dwelling E-newsletter
to get the newest information about options, issues occurring in our neighborhood and
different information about constructing an Open Dwelling; straight into your inbox.
The Cloudflare integration no longer relies on ipify.org to determine your IP,
but instead is using the whoami service.
Which means in case you have configured your community solely to permit site visitors there,
you would want to regulate it to permit for the brand new state of affairs.
The scan interval (
scan_interval) possibility within the Glances configuration is
eliminated, and the replace interval will use the default worth (60 seconds).
You probably have already configured Glances integrations, the beforehand saved interval
possibility will nonetheless be used. To revert to the default replace interval,
it’s essential re-add the mixing.
You need to use the
homeassistant.update_entity service in an automation
for customized replace intervals.
Media participant teams containing gamers that present an invalid media participant
entity state, will now report a “Unknown” group state.
The record of legitimate media participant states is accessible in our
The HERE Journey Time integration now makes use of the HERE API v8.
publicTransportTimeTable has been merged into
Your configuration will likely be migrated mechanically;
no guide interplay is critical.
(@eifinger – #80892) (documentation)
The unit system is now not managed by an choices setting of the HERE
Traveltime integration however makes use of the built-in customized items configurable per
The gap sensor now makes use of kilometers as a default and have to be manually
configured if it was beforehand utilizing the imperial system.
The videoloss occasion has been faraway from the supported record. The occasion has
at all times been used as a keep-alive for many Hikvision gadgets, and the library
makes use of it internally. Leaving it enabled as an possibility causes all the things to interrupt
if the occasion is definitely processed, so it was eliminated to remove confusion.
Any custom-made choices specified within the YAML configuration for a videoloss
occasion will have to be eliminated, and videoloss entities will now not be
generated by the mixing.
For those who used any of those entities in your automations or scripts, you’ll
have to replace these to take away using these entities.
The occasions fired when the cell app scanned a Tag had an incorrect machine ID;
This has been corrected.
Consequently, the evens now comprise a special however right machine ID. For those who
relied on the machine ID in your automations, you would possibly want to regulate these
with the brand new machine ID.
The identify of the mapping keys used for outlining HVAC modes within the Modbus
local weather integration (launched in 2022.11) has modified. This was wanted
to repair a difficulty with the
off key, which has a special which means in YAML.
As an alternative of:
hvac_mode_register: handle: ... values: off: 0 warmth: 1 cool: 2
You now have to make use of:
hvac_mode_register: handle: ... values: state_off: 0 state_heat: 1 state_cool: 2
YAML configuration of MQTT entities underneath the platform key (e.g.,
which was deprecated in Dwelling Assistant Core 2022.6, is now not supported.
The configuration should as a substitute be achieved underneath the
The legacy MQTT machine tracker is now not supported. See
the documentation for the supported MQTT
machine tracker configuration.
As of this launch, it is best to now use the trendy configuration schema for all
manually configured MQTT entities. Please observe that this doesn’t influence
MQTT discovery, for instance, Zigbee2MQTT.
(@jbouwh – #82102) (documentation)
encoding configuration possibility for the MQTT digital camera set to
was beforehand deprecated and has now grow to be an invalid configuration.
The brand new
image_encoding configuration possibility is now used to set Base64 encoding.
Please use the brand new
image_encoding config parameter (set to
b64) as a substitute.
The beforehand deprecated YAML configuration of the Radarr
integration has been eliminated.
Radarr is now configured by way of the UI, any present YAML
configuration has been imported in earlier releases and might now be safely
eliminated out of your YAML configuration recordsdata.
The unit of measurement for the charging energy sensor has been corrected.
Because the unit has modified, it should create a long-term statistics warning
that it’s essential resolve within the statistics builders instruments manually.
(@epenet – #81412) (documentation)
You’ll need to resolve the analytics warning by adjusting the earlier unit.
bypassed attribute in Risco zones has been eliminated and changed with
a swap. The matching companies have additionally been eliminated, and you may bypass
and un-bypass a zone utilizing the common swap companies
For instance, when you had a name to:
service: risco.bypass_zone goal: entity_id: binary_sensor.motion_bedroom
You may substitute it with:
service: swap.turn_on goal: entity_id: swap.motion_bedroom_bypassed
statistics sensor attribute has been eliminated and
changed by the extra versatile
For those who use the
quantiles attribute, you will want to adapt your sensor
configuration to recreate an identical values with the
(@ThomDietrich – #81749) (documentation)
The configuration of
statistics sensors has modified:
state_characteristic configuration setting is now necessary.
sampling_size configuration setting is now elective and now not
defaults to the arbitrary worth 20. Now you can outline
max_age, or each relying in your use case. Current sensors received’t behave
in a different way by the change. Nonetheless, you would possibly wish to examine whether or not your
presently outlined sensors have a significant
sampling_size configured or if
you want to take away this setting altogether.
(@ThomDietrich – #81749) (documentation)
As new PoE entities had been launched with 2022.11, this launch, the outdated
troublesome PoE consumer implementation that these entities changed,
has been eliminated. Upgrading will mechanically take away the outdated entities.
Please observe that the brand new PoE entities are disabled by default and characterize
every PoE-capable port with out mapping it to a consumer.
In case you are a customized integration or theme developer and wish to study
breaking modifications and new options accessible to your integration: Remember to
comply with our developer blog.
The next are probably the most notable for this launch:
Farewell to the next
The next integrations are additionally now not accessible as of this launch:
Google Chat has been eliminated. It relied on the Google Hangouts APIs,
which have been shut down, rendering the mixing unusable.
In fact, there may be much more on this launch. You’ll find a listing of
all modifications made right here: Full changelog for Dwelling Assistant Core 2022.12