House Assistant Core 2022.11! š
This November already feels quite a bit like Christmas š, what a heck of a
launch! Fairly just a few recommendations from the Month of āWhat the Heck?!ā
already landed! Able to unpack the presents? š
Speaking concerning the WTH month, it ended. Effectively, type of, a minimum of. It’s now closed
for brand new subjects/recommendations, however existing ones
stay open for dialogue and might be voted on. Iām curious to see extra of
these WTHs being resolved within the upcoming releases.
This launch has a lot goodness that I’ve a tough time selecting a favourite.
Water utilization, perhaps? Iām actually undecided, so Iām going to chop this intro quick.
Let me know your favourite within the feedback under!
Benefit from the launch!
../Frenck
PS: There might be no launch celebration stay stream this month,
as an alternative join us on the
State of the Open Home on
Sunday, November 13, 2022 (11:00 AM PST / 20:00 CET).
Tile card
This release introduces a new Dashboard card: the āTileā!
The tile card is a lovely little card that provides a quick overview of an
entity. The icon can be tapped to toggle the entity, and the rest of the card
brings up the āmore infoā dialog.
Read more about the Tile card in the documentation.
This first iteration of the Tile card is one of the first cards added this
release, that brings in a new style of card into Home Assistant.
Curious to find out what else will be coming? Join us for the State
of the Open Home live stream. Go to YouTube and click the bell š
so that you get notified once we go stay!
Statistic card
Extra playing cards! We have already got the Statistics Graph card,
which can be used to display graphs of long-term statistics of an entity.
This release brings the āStatisticā card!
The āStatisticā card, as the name implies, can show a single value of an entity,
based on the long-term statistics stored of that entity.
For example, want to display the average temperature of your living room this
week on your dashboard? The average power usage of your home today? The peak
power production of your solar panels today?
Yes, all of the above, this card can do!
Read more about the Statistic card in the documentation.
Smarter reloading of automation & scripts
WTH do all automations get reloaded when you change any of them?
Good query! And that WTH matter bought over 180+ votes as effectively!
Once you change a single automation or script by way of the editors within the person
interface (or reload your YAML-based ones), all of them get reloaded. This
means if they’re operating, ready for one thing (a delay, an occasion, or for an
entity to be in a sure state for X time), they’d all be reset.
This launch modifications this conduct, resolving that WTH! Solely automations that
are literally modified are reloaded. All others will stay operating and untouched.
This works when enhancing an automation within the UI, and even when reloading your
YAML-based automations in any break up YAML setup you might need.
Oh, as an added bonus: We utilized the very same for scripts too!
Getting insights into water usage
Since Home Assistant added energy management, tracking the usage of waterš°
has been requested quite a bit. It was raised again during this month of WTH,
and with over 370 votes, it’s clearly wished quite a bit.
This launch provides the flexibility to observe your water utilization within the vitality dashboard!
Though water isn’t strictly āvitalityā, it’s nonetheless a valuable resource
to trace. It’s typically tightly coupled with vitality utilization (like gasoline) when utilizing
scorching water, and the gained perception will help you cut back your ecological footprint
through the use of much less water š.
Some integrations, like Flo, Flume, and
HomeWizard Power, have been adjusted to help
monitoring water. Moreover, you possibly can create your individual utilizing templates, MQTT,
or ESPHome (requires ESPHome version 2022.10.1 or newer).
Try the documentation for the {hardware} choices
accessible to trace your water utilization or methods to construct your individual water utilization
sensors.
Color temperatures in Kelvin
Another WTH topic
that was voted for nearly 150 occasions! Why doesnāt House Assistant use Kelvin
for colour temperatures?
Effectively, a small piece of historical past: The House Assistant story began utilizing Philips
Hue a protracted, very long time in the past. And Hue makes use of mired for its colour temperature,
not Kelvin.
However right this moment, Kelvin is rather more generally used. It’s even on packages of the
bulbs you purchase. So, as of right this moment, House Assistant makes use of Kelvin too!
Kelvin is now the first colour temperature unit. This implies all lights
and every part colour temperature associated proven within the person interface,
are actually in Kelvin.
We nonetheless do help the great previous mired. Mireds are nonetheless working and
robotically transformed when wanted, so this isn’t a breaking change š
Moreover, integrations can now optionally use Kelvin immediately if the
machine or service accepts that. HomeKit, Shelly,
AVM FRITZ!SmartHome, and LIFX are all now utilizing Kelvin natively.
Long-term statistics in the entity dialogs
The āmore infoā dialogs of entities now use long-term statistics for
the graphs shown. It makes those dialogs a lot faster, especially on
mobile devices.
The first day of the week
The start of the week can differ for many of us. Your week will start on
Saturday, Sunday, or Monday based on where you are, your locale, or maybe
personal preference. As pointed out in
this WTH topic.
House Assistant will attempt to auto-detect the proper day to start out the week
based mostly on data supplied by your browser. Nonetheless, if it can’t detect it,
or in case you’ve gotten a private desire, now you can set it in your person profile.
Now you can set the day to start out the week at in your user profile.
Setting it implies that all date inputs, date vary pickers, schedules, calendars,
and even time situations in automations, will take this into consideration when
displaying weeks.
New templating features
We also have some great new advanced features added to templating this release!
Originating from this WTH topic:
Now you can use the state_attr() and states() capabilities as a filter,
and the is_state() and is_state_attr() capabilities can now be used as checks.
The common() operate now accepts a default worth, which might be useful
if no common might be calculated.
Lastly, the config_entry_id() template technique has been added, which permits
you to search for native IDs of integration configuration entries utilizing one
of the entities it gives.
For extra data on these new options and the House Assistant templating
capabilities typically, try the documentation.
Other noteworthy changes
There is much more juice in this release; here are some of the other
noteworthy changes this release:
- The default dashboard theme has been adjusted to move a little closer to the
new Material Design 3 guidelines. Borders around cards are now outlined
(instead of having a shadow), and corners are a little more rounded. - The automations and the devices dashboards now have icons on each row, making
them look all nice and shiny. Thanks, @bramkragten & @frenck. - The unit of measurement for entities offering Gasoline can now be modified and
transformed from the UI. Thanks, @emontnemery! - House Assistant is now discoverable by way of UPnP/SSDP, which means your occasion will
present up in your Home windows Community. Thanks, @StevenLooman! -
Shelly Gen2 gadgets that sleep (battery-powered) are actually supported!
Thanks, @thecode! - Now you can use sensors offering Gigajoule (GJ) with the vitality dashboard.
Thanks, @emontnemery! - The MQTT integration now has help for replace entities! Thanks, @bieniu!
- Media participant help was added to the Jellyfin integration. Thanks, @Ongy!
- The statistics card now helps āweekā as a potential interval. Thanks, @mib1185!
- The Solar situation can now deal with setting each earlier than & after on the similar
time. Thanks, @janick! - The āforked-daapdā mission was renamed to āOwntoneā. The combination was now
renamed Owntone too! Thanks, @uvjustin! -
Totally Kiosk Browser now gives a service to remotely change URLs in your
wall-mounted pill. Thanks, @cgarwood! - The Xiaomi Miio integration now helps the Xiaomi Air purifier 4 Lite and
the Roborock S7 MaxV. Thanks, @alexdrl & @starkillerOG! - The UniFi integration now gives particular person PoE management per port for
the consumer and machine PoE (switches are disabled by default).
Thanks, @Kane610! - The HomeKit Controller integration now helps encrypted Bluetooth
notifications, lowering state change latency and the variety of energetic BLE
connections made to gadgets. - When organising a brand new Generic Digital camera, you can be offered with a preview
of the digicam exhibiting you if it really works. Good! Thanks, @davet2001! - Help for
unique_ids was added to the next (YAML succesful) integrations:
New Integrations
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.11.1 – November 3
Release 2022.11.2 – November 8
Release 2022.11.3 – November 16
Release 2022.11.4 – November 20
Release 2022.11.5 – November 30
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 mounted! Or, test 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 taking place in our group and
different information about constructing an Open House; straight into your inbox.
Breaking Changes
Below is a listing of the breaking change for this release, per subject or
integration. Click on one of those to read more about the breaking change
for that specific item.
Multiple integrations provide sensors with the revolutions per minute unit.
Two units have been used throughout Home Assistant to indicate this:
RPM and rpm.
This release standardizes all integrations to use the lowercase rpm variant.
The following integrations have been adjusted:
Home Assistant automatically handles this change of units. However, if you
record history externally (for example, using InfluxDB), you might need to
adjust to this change.
The beforehand deprecated YAML configuration of the Android IP Webcam
integration has been eliminated.
Android IP Webcam is now configured by way of 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 beforehand deprecated YAML configuration of the Anthem A/V Receivers
integration has been eliminated.
Anthem A/V Receivers are actually configured by way of the UI, any current YAML
configuration has been imported in earlier releases and might now be safely
eliminated out of your YAML configuration recordsdata.
(@gjohansson-ST – #79931) (documentation)
The UPS Final Self Take a look at sensor is renamed to UPS Self Take a look at Consequence and
a brand new UPS Final Self Take a look at sensor experiences time as an alternative of the outcome.
Chances are you’ll want to interchange sensor.ups_last_self_test with
sensor.ups_self_test_result in automations and scripts
referencing the sensor.ups_last_self_test entity.
(@definitio – #80773) (documentation)
The counter and remaining pages attributes of the sensors
drum remaining life, black drum remaining life, cyan drum remaining life,
magenta drum remaining life, and yellow drum remaining life have been
migrated to their very own devoted sensor entities.
In case you are utilizing these attributes in your automation or script, you’ll need
to undertake these for this transformation.
- The
callerchoice fromClickSend TTSnotify service has been eliminated, as
it prevented calls from being really made. - The default identify has been modified to
clicksend_ttsas an alternative of an empty identify; in any other case
the service would seem asnotify.notify. Now it can, by default, seem
asnotify.clicksend_tts. This would possibly affect your automation or script. - The recipientās telephone quantity now should match E.164 format.
(@CharlieBailly – #76669) (documentation)
The beforehand deprecated YAML configuration of the Coinbase
integration has been eliminated.
Coinbase is now configured by way of the UI, any current YAML
configuration has been imported in earlier releases and might now be safely
eliminated out of your YAML configuration recordsdata.
Organising the notify platform of the ecobee integration by a platform part
utilizing YAML configuration is now not supported. The ecobee platform part
below notify: might be safely eliminated out of your YAML configuration recordsdata.
The thermostat index might be specified through the use of the goal parameter within the
notify service name as an alternative.
HomeKit occasion ID assignments are actually steady between restarts to conform
with the HomeKit specs. This prevents equipment from shedding
monitor of providers between restarts, and improves stability with utilizing
Siri particularly with apple watches.
This variation might dramatically enhance the soundness and re-sync occasions of
media_player entities (all), digicam entities (all), fan entities (presets),
distant entities (exercise ones), swap entities (energy strips)
triggers (all) between restarts which was particularly
obvious when the house has many equipment.
As a result of the assignments have been beforehand unstable, it might be essential to make
a one-time adjustment of accent room assignments, favorites,
or re-pair digicam equipment after upgrading.
As older variations didn’t accurately set service identifier values, it might be
essential to unpair and re-pair some BLE gadgets or to delete duplicate
entities manually.
If the service identifiers have been loaded incorrectly when the machine was paired
with an older model, operations would possibly elevate StopIteration or RuntimeError
errors. You may right these by deleting the combination for that machine,
and doing a one-time re-pairing.
The backing unit and the API
of the machine itself makes use of 0-4 as a flame top setting. By dialogue
on the boards the group has determined 1-5 is a way more logical setting
for flame top, and accordingly, this has been applied.
For those who set the flame top utilizing automations or scripts, you’ll need to
adapt these to this transformation.
logger now not modifications the default log stage of House Assistant to debug
if used with out a worth for default. It
will now solely change the default log stage of House Assistant from a
warning to one thing else if the default is explicitly specified.
If you don’t specify default and wish House Assistant to have a
default log stage of debug, you’ll need so as to add this to your YAML configuration:
The beforehand deprecated YAML configuration of the Open Trade Charges
integration has been eliminated.
Open Trade Charges is now configured by way of the UI, any current YAML
configuration has been imported in earlier releases and might now be safely
eliminated out of your YAML configuration recordsdata.
(@gjohansson-ST – #79856) (documentation)
In case you are a customized integration developer and wish to find out about breaking
modifications and new options accessible in your integration: You’ll want to observe our
developer blog. The next are probably the most notable for this launch:
All modifications
In fact, there may be much more on this launch. You could find an inventory of
all modifications made right here: Full changelog for House Assistant Core 2022.11
