2022.12: It does matter! – Residence Assistant

The Cloudflare integration no longer relies on ipify.org to determine your IP,
but instead is using the whoami service.

Which means when you have configured your community solely to permit visitors there,
you would wish to regulate it to permit for the brand new scenario.

(@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).

In case you have already configured Glances integrations, the beforehand saved interval
possibility will nonetheless be used. To revert to the default replace interval,
you should re-add the combination.

You should 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 listing of legitimate media participant states is obtainable 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 probably be migrated mechanically;
no handbook interplay is important.

(@eifinger – #80892) (documentation)

The unit system is not managed by an choices setting of the HERE
Traveltime integration however makes use of the built-in customized models configurable per
entity.

The gap sensor now makes use of kilometers as a default and should be manually
configured if it was beforehand utilizing the imperial system.

(@eifinger – #79159) (documentation)

The videoloss occasion has been faraway from the supported listing. 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 every thing to interrupt
if the occasion is definitely processed, so it was eliminated to eradicate confusion.

Any custom-made choices specified within the YAML configuration for a videoloss
occasion will have to be eliminated, and videoloss entities will not be
generated by the combination.

In the event you 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 probably be modified to power_off.

In the event you relied on this state worth in your automations or script,
you could regulate to this alteration.

(@bieniu – #77491) (documentation)

The occasions fired when the cell app scanned a Tag had an incorrect gadget ID;
This has been corrected.

In consequence, the evens now comprise a special however right gadget ID. In the event you
relied on the gadget ID in your automations, you would possibly want to regulate these
with the brand new gadget ID.

(@balloob – #82820) (documentation)

The title 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 problem with the off key, which has a special which means in YAML.

As an alternative of:

hvac_mode_register:
  deal with: ...
  values:
    off: 0
    warmth: 1
    cool: 2

You now have to make use of:

hvac_mode_register:
  deal with: ...
  values:
    state_off: 0
    state_heat: 1
    state_cool: 2

(@avishorp – #81749) (documentation)

YAML configuration of MQTT entities below the platform key (e.g., gentle),
which was deprecated in Residence Assistant Core 2022.6, is not supported.
The configuration should as an alternative be performed below the mqtt key.

The legacy MQTT gadget tracker is not supported. See
the documentation for the supported MQTT
gadget 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 digicam 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 an alternative.

(@jbouwh – #82244) (documentation)

The beforehand deprecated openuv.replace, openuv.update_uv_index,
and openuv.update_protection_data providers 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 current YAML
configuration has been imported in earlier releases and may now be safely
eliminated out of your YAML configuration information.

(@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 would create a long-term statistics warning
that you should resolve within the statistics builders instruments manually.

(@epenet – #81412) (documentation)

You will have to resolve the analytics warning by adjusting the earlier unit.

The bypassed attribute in Risco zones has been eliminated and changed with
a change. The matching providers have additionally been eliminated, and you may bypass
and un-bypass a zone utilizing the common change providers
(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 exchange it with:

service: change.turn_on
goal:
  entity_id: change.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.

In the event you use the quantiles attribute, you have to 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 obligatory.

The sampling_size configuration setting is now non-compulsory and not
defaults to the arbitrary worth 20. Now you can outline sampling_size,
max_age, or each relying in your use case. Current sensors gained’t behave
in a different way by the change. Nonetheless, you would possibly need to test whether or not your
at the moment 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 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 have been launched with 2022.11, this launch, the previous
troublesome PoE consumer implementation that these entities changed,
has been eliminated. Upgrading will mechanically take away the previous entities.

Please observe that the brand new PoE entities are disabled by default and symbolize
every PoE-capable port with out mapping it to a consumer.

(@Kane610 – #81749) (documentation)