2023.4: Customized template macros, and plenty of extra new entity dialogs!

(@epenet – #88694) (documentation)

The binary sensor offering out there firmware updates has been deprecated
since 2022.5 and is now eliminated. Use the brand new replace entity as a substitute.

(@mib1185 – #89940) (documentation)

This variation solely impacts Dwelling Assistant situations operating immediately on
MacOS (not inside a digital machine).

Any integration or gadget beforehand arrange utilizing a UUID Bluetooth
handle will must be deleted and recreated.

(@bdraco – #89926) (documentation)

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 may now be safely faraway from
your YAML configuration information.

(@frenck – #89239) (documentation)

AQI sensor state values at the moment are in English, and the person interface will
show their translation for the chosen language. In case you have been utilizing
this sensor in your automations and scripts, you’ll want to regulate these for
this modification.

(@bieniu – #89044) (documentation)

The identify and station sensor state attributes have been eliminated as a result of
they’re static knowledge 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.

(@bieniu – #89389) (documentation)

The habits of passing parameters to service calls focusing on notification
teams has modified.

Present habits: knowledge mappings configured within the service override
mappings configured within the motion.

New habits: knowledge mappings configured within the motion override
mappings configured within the service.

(@arychj – #90253) (documentation)

As a way to acquire an up-to-date record of suitable packages in your home equipment, it is going to be essential to reconfigure the combination.

Please be aware that as a result of limitations on the Dwelling Join facet, it is very important have your home equipment Turned on throughout the reconfiguration course of.

This motion is a one-time requirement.

(@stickpin – #88801) (documentation)

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 may now be safely faraway from
your YAML configuration information.

(@jbouwh – #89981) (documentation)

The conversion to MWh and the corresponding MWh-entities have been eliminated.

To resolve the breaking change :

• For those who make use of any of sensor.heat_meter_heat_usage or
  sensor.heat_meter_heat_previous_year for automations, scripts, and so on.,
  you possibly can substitute these with the GJ-entities sensor.heat_meter_heat_usage_gj
  and sensor.heat_meter_heat_previous_year_gj.
• If relevant, within the vitality dashboard, substitute sensor.heat_meter_heat_usage
  with sensor.heat_meter_heat_usage_gj. Observe that the vitality dashboard will
  nonetheless convert to MWh or kWh, due to this fact leading to the identical values as earlier than.

(@vpathuis – #89522) (documentation)

Logbook can be unavailable till the database schema migration completes.
Logbook script and automation traces from earlier runs of Dwelling Assistant
can be unavailable till background knowledge 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 now not show context data
for these occasions within the logbook tab.

(@bdraco – #89945) (documentation)

• 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 a substitute use the textual content.set_value service and the corresponding
  textual content entity as a goal.
• The MySensors IR change entity, equivalent to an S_IR baby with
  V_SEND worth, has been eliminated. This entity hasb been deprecated since
  2023.2.0. It’s been changed by a distant entity.
• It is best to replace any automations or scripts that use the mysensors.send_ir_code
  service to as a substitute use the distant.send_command service and the corresponding
  distant entity as a goal. Related adjustments must be made for actions utilizing
  the change.turn_on and switch_turn_off companies focusing on the eliminated
  IR change entities. Exchange these with distant.turn_on and distant.turn_off
  companies and distant entity 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 may now be safely faraway from
your YAML configuration information.

(@frenck – #89161) (documentation)

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 remains 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 may now be safely
eliminated out of your YAML configuration information.

(@jbouwh – #87987) (documentation)

The choice to outline your personal scan interval has been eliminated, knowledge is now
up to date each 60 seconds.

(@mib1185 – #89396) (documentation)

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 now not overwritten and is now the identical as
areas in each template. The brand new default template is now:

This good house is managed by Dwelling Assistant.

An summary of the areas and the units on this good house:
{%- 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 in regards to the world in truth.

If the person needs to regulate a tool, reject the request and counsel utilizing the Dwelling Assistant app.

(@balloob – #90481) (documentation)

The open and shut instructions for the io:CyclicGarageOpenerIOComponent gadget
Have been eliminated, see this concern
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 isn’t a state returned and no clear open and shut command.

Just one command is obtainable: cycle. A button is an ideal match for this
use case and take away all confusion; this button entity has been added this
launch.

(@tetienne – #89043) (documentation)

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 may 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 may now be safely faraway from
your YAML configuration information.

(@gjohansson-ST – #90284) (documentation)

Outsized occasions with knowledge bigger than 32KiB are now not recorded
to keep away from overloading the database and polluting the reminiscence cache.

(@bdraco – #90747) (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 may 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 may now be safely faraway from
your YAML configuration information.

(@frenck – #89166) (documentation)

Tasmota sensor now not units the force_update flag to True.

Tasmota binary_sensor now 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 are not any
longer supported in restricted templates.

(@Petro31 – #86815)

Enumerating states utilizing templates are now not sorted by
entity_id by default, because it was computationally costly.

To revive the unique habits, a type filter could be added to any
present template utilizing the under instance:

 type(attribute='entity_id') %

The habits of the brink binary sensor has modified:

• The edge binary sensor’s state is reset to unknown when 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 being unknown, unavailable, or not a legitimate float:
  • Initialize a threshold sensor with solely a decrease threshold to state off,
    with the place attribute set to above.
  • Initialize a threshold sensor with solely a upperthreshold to state off,
    with the place attribute set to under.
  • Initialize a threshold sensor with solely an higher and a decrease threshold
    to state on, with the place attribute set to in_range.

(@emontnemery – #88978) (documentation)

The tip-date for rubbish assortment occasions on the calendar entity, will now
be in the future 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 may now be safely faraway from
your YAML configuration information.

(@gjohansson-ST – #90288) (documentation)

With this launch, you’ll need to replace your zwave-js-server occasion.
It’s essential to use zwave-js-server 1.27.0 or better (schema 27).

• For those who use the Z-Wave JS add-on, you want a minimum of model 0.1.77.
• For those who use the Z-Wave JS UI add-on, you want a minimum of model 1.8.1.
• For those who use the Z-Wave JS UI Docker container, you want a minimum of model 8.11.1.
• For those who run your personal Docker container or another set up methodology, you
  might want to replace your zwave-js-server occasion to a minimum of 1.27.0.

(@raman325 – #90212) (documentation)