2022.12: It does matter! – Dwelling Assistant

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.

(@ludeeus – #81714) (documentation)

The beforehand deprecated guardian.disable_ap and guardian.enable_ap service
and the corresponding binary sensor have now been eliminated.

(@bachya – #81056) (documentation)

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.

(@engrbm87 – #72748) (documentation)

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
developer documentation.

(@epenet – #78465) (documentation)

The HERE Journey Time integration now makes use of the HERE API v8.
Travelmode publicTransportTimeTable has been merged into publicTransport.
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
entity.

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.

(@eifinger – #79159) (documentation)

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.

(@mezz64 – #81173) (documentation)

The PowerOff state of the choose entity will likely be modified to power_off.

For those who relied on this state worth in your automations or script,
you need to regulate to this variation.

(@bieniu – #77491) (documentation)

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.

(@balloob – #82820) (documentation)

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

(@avishorp – #81749) (documentation)

YAML configuration of MQTT entities underneath the platform key (e.g., mild),
which was deprecated in Dwelling Assistant Core 2022.6, is now not supported.
The configuration should as a substitute be achieved underneath the mqtt key.

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)

The encoding configuration possibility for the MQTT digital camera set to b64
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.

(@jbouwh – #82244) (documentation)

The beforehand deprecated openuv.replace, openuv.update_uv_index,
and openuv.update_protection_data companies have now be eliminated.

(@bachya – #81055) (documentation)

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.

(@tkdrob – #81210) (documentation)

The beforehand deprecated extra_water_on_hot_days and freeze_protection
binary sensors, and freeze_protection_temperature sensor have now been eliminated.

(@bachya – #81053) (documentation)

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.

The 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
(turn_on and turn_off respectively).

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

(@OnFreund – #81137) (documentation)

The beforehand deprecated simplisafe.clear_notifications service
has now been eliminated.

(@bachya – #81054) (documentation)

The quantiles statistics sensor attribute has been eliminated and
changed by the extra versatile percentile attribute.

For those who use the quantiles attribute, you will want to adapt your sensor
configuration to recreate an identical values with the percentile attribute.

(@ThomDietrich – #81749) (documentation)

The configuration of statistics sensors has modified:

The state_characteristic configuration setting is now necessary.

The sampling_size configuration setting is now elective and now not
defaults to the arbitrary worth 20. Now you can outline sampling_size,
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)

The Subaru API has modified and now not returns values required by two sensors:

• Exterior temp
• 12V battery voltage

These sensors have been faraway from the Subaru integration.

(@G-Two – #83213) (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.

(@Kane610 – #81749) (documentation)