2023.4: Customized template macros, and lots of extra new entity dialogs!
Dwelling Assistant Core 2023.4! š
The spring (launch) is right here! And do now we have some high-quality new options for you
to play with this upcoming easter weekend! š°
Iām thrilled to see extra of these new entity dialogs coming on this launch.
They appear stunning and work exceptionally properly from the cellular app. There’s
even an added bonus of recent Tile card options! Howeverā¦
Oh boy, do I really like the brand new means to make your personal Jinja2 template macros in
this launch. It’s mind-blowing! One of the best factor about them, it makes them
simply shareable as properly! Canāt wait to see what you all provide you with!
Completely happy Easter! š£ and benefit from the launch!
../Frenck
Donāt overlook to join our release party live stream on YouTube
5 April 2023, at 12:00 PDT / 21:00 CEST!
New dialogs for alarm, cowl, and fan entities
So, this release @piitaya saved on trucking, implementing the designs
by @matthiasdebaat, bringing the identical new clear and neat UI in entity dialogs
for alarm management panels, covers, and followers!
Covers
First up, covers! For covers, there are a lot of variants, doorways, home windows, curtains,
blinds, shutters, and so on. Not simply that, some may be managed by how far they
are open/closed, and others can solely be opened and closed.
That is no drawback for the brand new dialogs. They are going to alter to the capabilities
your cowl has:
The one on the left is fascinating, as the primary slider controls how far down
the blinds are. Discover the way it slides in from the highest! The slider immediately subsequent
to it controls the lean. Good!
Fans
Next up, the fan entities. The UI experience shown in the dialog will
automatically adjust to the capabilities of the fan you are controlling, just
like with covers.
Depending on the number of speed steps your fan has, the dialog will
automatically adjust the UI. In case it has four speed steps or less, it will
show the speed buttons as on the left screenshot. Otherwise, it will use the
slider shown on the most right screenshot.
Alarm control panels
Lastly, the alarm control panel entities. They are a bit different compared
to others as, more often, these require one to input a code to arm or disarm
the alarm.
This is how arming and disarming an alarm now looks like.
When needed, the pin-pad will pop up! A nice finishing touch is the neat little
animation is shown during the process of arming and disarming the alarm.
New features for the Tile card
The Tile card has two new features: Fan speed & Alarm mode.
Both look and feel similar to the new entity dialogs from above, making the look
and feel, nice and consistent. Take a look; arenāt they beautiful?
Like the new fan entity dialog, the fan speed feature will show buttons if there
are 4 speeds or less; in all other cases, it will use the slider. If the fan
can only be turned on/off, like the fan in the middle in the above screenshot,
the regular tile can be used.
The alarm mode feature allows quickly setting your alarm in a different state.
The feature provides the option to select which modes are shown as buttons in
the card.
Just like with the new entity dialog, the pin pad will pop up once a code entry
is needed and even the nice little animation is there. š¤©
Macros for your templates
If you are an advanced Home Assistant user, you most likely will be familiar
with Home Assistantās templating language: Jinja2. It allows you to do amazing
powerful things in your templates. However, if you have lots of them, you
often end up repeating similar logic everywhere!
@depoll to the rescue! He discovered a manner so as to add the power to centrally outline
your personal Jinja2 macros and import and use them wherever in Dwelling Assistant! š¤Æ
To help this, Dwelling Assistant now has a brand new custom_templates folder, the place
you possibly can retailer your macros. For instance, assume this file
/config/custom_templates/instruments.jinja:
% macro answer_question(entity_id) %
Is the state_attr(entity_id, 'friendly_name') on?
iif('Sure', 'No') !
% endmacro %
This macro answer_question will ask and reply a query based mostly on a given
entity ID. Now you can import and use this macro wherever in Dwelling Assistant.
For instance:
% from 'instruments.jinja' import answer_question %
answer_question('gentle.kitchen')
Which is able to output:
Is the kitchen gentle on?
Sure!
An implausible contribution! Thanks, @depoll!
Reusing templates documentation
More new templating features
As if the reusability of your macros wasnāt good enough already, there
is much more templating goodness in this release!
Thanks, @depoll, @ehendrix23, @petro31, and @rokam, for these superb
additions down beneath! ā¤ļø
Adjusted behavior of relative_time and today_at
@Petro31 alter the habits for template entities utilizing the relative_time
and today_at template capabilities to replace their state as soon as a minute. Good!
New is_hidden_entity function
The brand new is_hidden_entity function was added by @depoll, which might inform
if a given entity has been marked āhiddenā or not. This operate additionally works
as a check. Cool!
This instance returns an inventory of all entities within the kitchen space that aren’t
hidden.
reject('is_hidden_entity')
New areas function
Talking about areas, @rokam added an areas operate, which returns an inventory
of all areas you have got!
A simplistic instance:
Added break and continue for use in for loops
@depoll added help for break and proceed in for loops, which permits
short-circuiting these loops, permitting you to make them extra environment friendly.
%- for worth in vary(10) %
%- if worth == 1 -%
%- proceed -%
%- elif worth == 3 -%
%- break -%
%- endif -%
worth
%- endfor -%
New has_value function
Lastly, @ehendrix23 added a requested template operate from the Month of
āWhat the Heck?!ā: has_value. The has_value operate can be used as
check and might filter out entities at present in an unavailable or unknown
state.
You could possibly use this conditionally, like so:
% if has_value('sensor.train_departure_time') %
The prepare leaves at states('sensor.train_departure_time')
% endif %
Or, possibly listing all entities from the lounge that at present don’t have any state
worth:
reject('has_value')
Database scalability
As your smart home grows and you add more devices, this means more data to keep
track of. This release includes significant advancements to the recorder
database design to help Home Assistant scale.
This version has a new database format that reduces the space needed to store
history for your devices. This change comes with a few benefits:
- Smaller (deduplication), less disk usage
- Reduced disk IO (SD-card lifetime improvements)
- Reduced CPU-usage š
- Quicker startup šļø
- Faster history graphs and logbook
- Reduced latency in the entire system which means less waiting from the time
you hit a button until an action completes š - Home Assistant now keeps history when renaming entities š¤
If you are accessing the database directly, check out the Data Science Portal
and the SQL Integration for up to date instance queries.
It could take some time to finish background information migration, relying on the scale
of your saved information. To make sure Dwelling Assistant retains historical past when renaming an
entity, wait 24 hours after upgrading earlier than renaming.
New selector capabilities
Selectors are user inputs for the user interface
that drive things like Blueprints. A new selector for use
in Blueprints has been added by @emontnemery and @piitaya: The fixed selector.
The fixed selector supplies an elective enter, which returns a set worth
(the fixed) when enabled, in any other case doesnāt present any worth in any respect.
Instance use in a Blueprint:
instance:
identify: Fixed selector instance
selector:
fixed:
label: Enabled
worth: true
Which ends up in the next:
When checked, the selector returns the set worth.
Additionally improved are the gadget and entity filters on the Space,
Entity, Gadget, and Goal selectors. Beforehand, you possibly can filter with a
single set of circumstances; now, you possibly can move in an inventory of filters.
In case you are constructing Blueprints, this may be actually useful if a person ought to
be capable to choose one among a number of totally different gadgets.
An instance, this selector permits you to choose the battery sensor of
both a Philips Hue RWL020 (US) or RWL021 (EU) distant in your Blueprint.
gadget:
filter:
- integration: deconz
producer: Philips
mannequin: RWL020
- integration: deconz
producer: Philips
mannequin: RWL021
entity:
- area: sensor
device_class: battery
Translating entities
Over the past releases, weāve been slowly extending translation support in more
places in Home Assistant. This release completes support for translating
entities!
This includes the entitiesā names, their attributes, and translations of
the attribute values. These translations will be visible on your dashboards,
dialogs, automation editors, etc. Pretty much all places displaying them.
Integrations have to explicitly add support for these. Quite a few integrations
have done so in this release, but we expect many to follow in the upcoming
releases.
Other noteworthy changes
There are much more easter bunnies in this release; here are some of the other
noteworthy changes this release:
- @ArturoGuerra added help for locks to Matter! Good!
- The brand new gentle entity dialog (launched final launch) now higher helps
white mode. Thanks, @piitaya! -
@emontnemery added power storage and quantity storage gadget courses; these
will permit differentiating between, for instance, consumed power versus saved
power in a battery. -
@starkillerOG is rocking the Reolink integration. It now supplies button,
change, siren, choose, quantity, and lightweight entities for every kind of belongings you
Reolink cameras and doorbells can do. Superior! - The Common Media Participant now helps looking media! Thanks, @Drafteed!
- The Supervisor integration now supplies sensors containing the
Dwelling Assistant Core and Supervisorās stats. Thanks, @ludeeus! - The Spotify integration now helps podcasts! Good @BTMorton!
-
LIVISI Sensible Dwelling now helps local weather gadgets, switches (PSSO, ISS,
and ISS2), and window sensors (WDS). Thanks @StefanIacobLivisi & @planbnet! - ESPHome now helps pairing Bluetooth gadgets. Good work @bdraco & @jagheterfredrik!
-
@MarkGodwin prolonged the TP-Hyperlink Omada integration to help replace
entities; superior! - All
solar.solarentity attributes at the moment are additionally accessible as sensors, a lot
simpler to make use of, thanks @gjohansson-ST! - Covers with the door gadget class, now seem as precise doorways in HomeKit,
good @Dexwell! -
@loongyh did one thing comparable for Google Assistant. Covers with the
window gadget class now present up as precise home windows. Thanks! - The SQL integration now helps settings gadget and state courses, thanks @gjohansson-ST!
- @teharris1 added help for the brand new Insteon i3 gadget, cool!
New Integrations
This launch has no new integrations, however does present a few new digital
integrations. Digital integrations are stubs dealt with by different (present)
integrations to assist with findability. These are new:
Integrations now available to set up from the UI
The following integrations are now available via the Home Assistant UI:
Release 2023.4.1 – April 6
Release 2023.4.2 – April 8
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, verify 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 Dwelling Publication
to get the newest information about options, issues occurring in our neighborhood and
different information about constructing an Open Dwelling; straight into your inbox.
Breaking Changes
The previously deprecated YAML configuration of the Aladdin Connect integration
has been removed.
Aladdin Connect is now configured via the UI, any existing YAML configuration
has been imported in previous releases and can now be safely removed from
your YAML configuration files.
The calendar.create_event service now enforces that begin and finish dates are
unique. This has at all times been a part of the specification however was not clearly
documented and enforced.
(@allenporter – #89533) (documentation)
The beforehand deprecated YAML configuration of the DSMR Reader integration
has been eliminated.
DSMR Reader is now configured by way of the UI, any present YAML configuration
has been imported in earlier releases and might now be safely faraway from
your YAML configuration information.
AQI sensor state values at the moment are in English, and the person interface will
show their translation for the chosen language. If in case you have been utilizing
this sensor in your automations and scripts, youāll want to regulate these for
this transformation.
(@bieniu – #89044) (documentation)
The identify and station sensor state attributes have been eliminated as a result of
they’re static information that don’t describe the state of the entity.
The index sensor state attribute has been migrated to a separate entity,
for instance, sensor.home_no2_index.
The habits of passing parameters to service calls focusing on notification
teams has modified.
Present habits: information mappings configured within the service override
mappings configured within the motion.
New habits: information mappings configured within the motion override
mappings configured within the service.
The beforehand deprecated YAML configuration of the IMAP integration
has been eliminated.
IMAP is now configured by way of the UI, any present YAML configuration
has been imported in earlier releases and might now be safely faraway from
your YAML configuration information.
The conversion to MWh and the corresponding MWh-entities have been eliminated.
To resolve the breaking change :
- In case you make use of any of
sensor.heat_meter_heat_usageor
sensor.heat_meter_heat_previous_yearfor automations, scripts, and so on.,
you possibly can substitute these with the GJ-entitiessensor.heat_meter_heat_usage_gj
andsensor.heat_meter_heat_previous_year_gj. - If relevant, within the power dashboard, substitute
sensor.heat_meter_heat_usage
withsensor.heat_meter_heat_usage_gj. Word that the power dashboard will
nonetheless convert to MWh or kWh, due to this fact leading to the identical values as earlier than.
Logbook might be unavailable till the database schema migration completes.
Logbook script and automation traces from earlier runs of Dwelling Assistant
might be unavailable till background information migration is accomplished following
the schema migration.
(@bdraco – #88942 #89465) (documentation)
Automation and script traces that embrace state change occasions recorded with
Dwelling Assistant 2022.5.x or older will not show context data
for these occasions within the logbook tab.
- The MySensors notify platform has been eliminated. Itās been deprecated since
2023.2.0. Itās been changed by a textual content entity platform. - It is best to replace any automations or scripts that use the
notify.mysensors*
service to as an alternative use thetextual content.set_valueservice and the corresponding
textual content entity as a goal. - The MySensors IR
changeentity, similar to anS_IRyoungster with
V_SENDworth, has been eliminated. This entity hasb been deprecated since
2023.2.0. Itās been changed by adistantentity. - It is best to replace any automations or scripts that use the
mysensors.send_ir_code
service to as an alternative use thedistant.send_commandservice and the corresponding
distantentity as a goal. Comparable modifications ought to be made for actions utilizing
thechange.turn_onandswitch_turn_offcompanies focusing on the eliminated
IRchangeentities. Substitute these withdistant.turn_onanddistant.turn_off
companies anddistantentity targets.
(@MartinHjelmare – #90402 #90403) (documentation)
The beforehand deprecated YAML configuration of the Moon integration
has been eliminated.
Moon is now configured by way of the UI, any present YAML configuration
has been imported in earlier releases and might now be safely faraway from
your YAML configuration information.
The tls_version configuration parameter (deprecated June 2020) has been
eliminated. All different MQTT dealer settings have been moved to the UI earlier than.
When the tls_version setting continues to be in your YAML configuration, MQTT will
not begin up.
The beforehand deprecated MQTT dealer YAML configuration has been eliminated.
The MQTT dealer is now configured by way of the UI, any present MQTT dealer YAML
configuration has been imported in earlier releases and might now be safely
eliminated out of your YAML configuration information.
Your beforehand chosen mannequin has been reset to the brand new
and cheaper GPT 3.5 mannequin.
(@balloob – #90423) (documentation)
The built-in areas variable is not overwritten and is now the identical as
areas in each template. The brand new default template is now:
This sensible house is managed by Dwelling Assistant.
An summary of the areas and the gadgets on this sensible residence:
%- for space in areas() %
%- set area_info = namespace(printed=false) %
%- for gadget in area_devices(space) -%
%- if not device_attr(gadget, "disabled_by") and not device_attr(gadget, "entry_type") and device_attr(gadget, "identify") %
%- if not area_info.printed %
area_name(space) :
%- set area_info.printed = true %
%- endif %
- device_attr(gadget, "identify") string) not in (device_attr(gadget, "identify") ( device_attr(gadget, "mannequin") )% endif %
%- endif %
%- endfor %
%- endfor %
Reply the person's questions concerning the world in truth.
If the person desires to regulate a tool, reject the request and counsel utilizing the Dwelling Assistant app.
The open and shut instructions for the io:CyclicGarageOpenerIOComponent gadget
Have been eliminated, see this issue
for extra particulars on this gadget.
To sum up, this gadget is a storage door however can’t be uncovered as such inside
Dwelling Assistant. There is no such thing as a state returned and no clear open and shut command.
Just one command is out there: cycle. A button is an ideal match for this
use case and take away all confusion; this button entity has been added this
launch.
The beforehand deprecated YAML configuration of the Pushbullet integration
has been eliminated.
Pushbullet is now configured by way of the UI, any present YAML configuration
has been imported in earlier releases and might now be safely faraway from
your YAML configuration information.
(@gjohansson-ST – #90285) (documentation)
The beforehand deprecated YAML configuration of the Radio Thermostat integration
has been eliminated.
Radio Thermostat is now configured by way of the UI, any present YAML configuration
has been imported in earlier releases and might now be safely faraway from
your YAML configuration information.
(@gjohansson-ST – #90284) (documentation)
The beforehand deprecated YAML configuration of the Scrape integration
has been eliminated.
Scrape is now configured by way of the UI, any present YAML configuration
has been imported in earlier releases and might now be safely faraway from
your YAML configuration information.
(@gjohansson-ST – #90272) (documentation)
The beforehand deprecated YAML configuration of the Season integration
has been eliminated.
Season is now configured by way of the UI, any present YAML configuration
has been imported in earlier releases and might now be safely faraway from
your YAML configuration information.
Tasmota sensor not units the force_update flag to True.
Tasmota binary_sensor not units the force_update flag to True, besides
for binary_sensor mapped to a Tasmota change with switchmode set to 13 or 14.
(@DerEnderKeks – #85943) (documentation)
The relative_time and today_at template capabilities and filters aren’t any
longer supported in restricted templates.
Enumerating states utilizing templates are not sorted by
entity_id by default, because it was computationally costly.
To revive the unique habits, a type filter may be added to any
present template utilizing the beneath instance:
% for state in states
The habits of the brink binary sensor has modified:
- The edge binary sensorās state is reset to
unknownwhen the monitored
sensorās state is unknown, unavailable, or not a legitimate float. - When the monitored sensorās state is first legitimate, or when itās legitimate
after beingunknown,unavailable, or not a legitimate float:- Initialize a threshold sensor with solely a decrease threshold to state
off,
with theplaceattribute set toabove. - Initialize a threshold sensor with solely a upperthreshold to state
off,
with theplaceattribute set tobeneath. - Initialize a threshold sensor with solely an higher and a decrease threshold
to stateon, with theplaceattribute set toin_range.
- Initialize a threshold sensor with solely a decrease threshold to state
(@emontnemery – #88978) (documentation)
The top-date for rubbish assortment occasions on the calendar entity, will now
be someday later in comparison with the beginning date. It’s because in calendaring,
the end-date is unique.
(@bobvandevijver – #89028) (documentation)
The beforehand deprecated YAML configuration of the Volvo On Name integration
has been eliminated.
Volvo On Name is now configured by way of the UI, any present YAML configuration
has been imported in earlier releases and might now be safely faraway from
your YAML configuration information.
(@gjohansson-ST – #90288) (documentation)
With this launch, you will have to replace your zwave-js-server occasion.
You should use zwave-js-server 1.27.0 or larger (schema 27).
- In case you use the
Z-Wave JSadd-on, you want a minimum of model0.1.77. - In case you use the
Z-Wave JS UIadd-on, you want a minimum of model1.8.1. - In case you use the
Z-Wave JS UIDocker container, you want a minimum of model8.11.1. - In case you run your personal Docker container or another set up technique, you
might want to replace yourzwave-js-serveroccasion to a minimum of1.27.0.
In case you are a customized integration developer and need to find out about breaking
modifications and new options accessible to your integration: Make sure to comply with our
developer blog. The next are essentially the most notable for this launch:
Farewell to the following
The following integrations are also no longer available as of this release:
-
Dark Sky has been removed. Apple acquired Dark Sky, and the API has now
been shut down. (@gjohansson-ST – #90322) -
Magicseaweed has been eliminated. Magicseedweed not supplies API keys
to customers. Moreover, the mixing is not in a practical state.
(@gjohansson-ST – #90277)
All modifications
After all, there may be much more on this launch. Yow will discover an inventory of
all modifications made right here: Full changelog for Dwelling Assistant Core 2023.4
