2023.5: Let’s speak! – Residence Assistant

(@bieniu – #91492) (documentation)

The “Android TV” integration has been renamed to “Android Debug Bridge”.

This rename is as a result of that’s what it really managed/supplied. With
the addition of the Android TV Distant integration on this launch, we wished
to cut back doable confusion sooner or later.

(@tronikos – #90657) (documentation)

All YAML configuration choices for the historical past integration have been eliminated
as they have been now not utilized by the frontend.

(@bdraco – #90992) (documentation)

The min/max goal humidities for (de)humidifier gadget uncovered over HomeKit
has modified. The HomeKit UI will now present the true relative humidity. When
the slider in HomeKit goes above or under the max/min set humidity, it is going to
be set again to the max/min allowed humidity.

(@stackia – #90854) (documentation)

Default HomeKit to hear on all interfaces to match Residence Assistant conduct.
To restrict HomeKit to particular community interfaces, specify an deal with
in configuration.yaml.

(@bdraco – #91520) (documentation)

The usage of imap_content occasion might break for customers that need to parse information
from bigger e-mail messages from the truncated half. Solely the primary 2048
bytes of the message physique (2 KiB) shall be obtainable.

(@jbouwh – #92066) (documentation)

The silence choice for DynamicShutter has been eliminated as a result of it brought on the
cowl entity to be non-functional if it didn’t assist silence. This
performance shall be reintroduced in a future launch.

(@iMicknl – #91354) (documentation)

For Reolink doorbells, the “Standing LED” mild entity is changed by a
“Standing LED” choose entity. The change off state corresponds to the choose
Auto, and the change on state corresponds to the choose
Auto & at all times on at night time. A further Keep off state is now obtainable.

(@starkillerOG – #90469) (documentation)

• Muted teams with stream enjoying can have state idle as a substitute of enjoying.
• Related shoppers is not going to have state on anymore however use the identical states as
  teams: idle and enjoying.
• Disconnected shoppers have state standby as a substitute of off as a result of the
  Snapcast server nonetheless accepts instructions.

(@luar123 – #77449) (documentation)

The unit conversion for all reminiscence, storage, and community utilization-related
sensors was corrected from binary (1024) to decimal (1000) base to be in
line with the used measurement models (eq. MB = 1.000.000 bytes).

It’s possible you’ll must replace the traditionally recorded models for these sensors through
the statistics web page beneath developer instruments.

(@mib1185 – #90633) (documentation)

The ensure_ascii argument for to_json in Jinja templates now defaults to
False, permitting us to make use of a sooner JSON encoder by default.

This shouldn’t be a problem for many, as JSON parsers broadly settle for Unicode
enter. Should you nonetheless must encode Unicode characters inside JSON strings,
set ensure_ascii to True explicitly to revive the previous conduct.

(@depoll – #91253)

UniFi integration now not gives each hostname and host_name attributes
for a consumer tracker entity. Solely host_name shall be supplied as an attribute.

(@Kane610 – #91188) (documentation)

The earlier deprecated set_doorbell_message service has been eliminated. Use
the textual content entity for the UniFi Defend LCD display as a substitute.

(@AngellusMortis – #91523) (documentation)

The beforehand deprecated YAML configuration of the Common Gadgets ISY/IoX
integration has been eliminated.

Common Gadgets ISY/IoX is now configured through the UI. Any current YAML
configuration has been imported in earlier releases and might now be safely
eliminated out of your YAML configuration recordsdata.

(@shbatm – #91575) (documentation)

The built-in proportion unit % is now used for relative humidity and absolute
humidity as a substitute of the customized models %RH and %AH, respectively.

(@shbatm – #90863) (documentation)

The next customized ISY994 providers have been eliminated:

• reload
• cleanup_entities
• system_query
• set_ramp_rate
• set_on_level
• run_network_resource
• set_variable

These providers had been beforehand deprecated in favor of built-in providers
and quantity, choose, and button entities. Please replace your automations
and dashboards to make use of the brand new entities and/or built-in providers in case you have
not already.

(@shbatm – #91569) (documentation)

Nightfall/Daybreak nodes on Insteon Movement Sensors now have their states inverted to
appropriately present “Mild detected” throughout daylight and “No mild” when the nightfall
sensor is energetic.

That is reversed from earlier conduct. Should you depend on this sensor in your
automations, they have to be up to date.

(@shbatm – #92035) (documentation)

Two new Webhook set off choices have been added that restrict how a webhook can
set off an automation. A brand new allowed_methods choice can be utilized to regulate
which HTTP request strategies can activate the set off (GET, HEAD, POST, and
PUT). And the local_only choice is used to permit units exterior your native
community to activate the set off.

Beforehand all webhook triggers may very well be activated by HEAD, POST, and PUT
strategies from any gadget (native or on the web). With the brand new choices, solely
POST and PUT are enabled by default.

In Residence Assistant Core 2023.7, any webhook set off that doesn’t set local_only
to false can solely be activated by units on the identical community as Residence Assistant.

Click on the gear/cog icon beside the Webhook ID to replace your webhook triggers.
Then choose an applicable worth for Solely accessible from the native community.
It’s essential to deselect the choice for the Save button to seem. Then
reselect the choice if it ought to be enabled. It will make the restore warning
go away.

See the webhook set off documentation
for an outline of the brand new choices. And please evaluation the brand new
Webhook Safety part for greatest
practices when utilizing webhook triggers.

(@esev – #66494) (documentation)

With this launch, you’ll need to replace your zwave-js-server occasion.
You could use zwave-js-server 1.28.0 or higher (schema 28).

• Should you use the Z-Wave JS add-on, you want not less than model 0.1.79.
• Should you use the Z-Wave JS UI add-on, you want not less than model 1.11.2.
• Should you use the Z-Wave JS UI Docker container, you want not less than model 8.14.2.
• Should you run your personal Docker container or another set up methodology,
  you’ll need to replace your zwave-js-server occasion to not less than 1.28.0.

(@raman325 – #91989) (documentation)