Home Assistant Core 2022.11.0 → 2022.12.0

Cloudflare

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

This means that if you have configured your network only to allow traffic there, you would need to adjust it to allow for the new situation.

(@ludeeus - #81714) (documentation)

Elexa Guardian

The previously deprecated guardian.disable_ap and guardian.enable_ap service and the corresponding binary sensor have now been removed.

(@bachya - #81056) (documentation)

Glances

The scan interval (scan_interval) option in the Glances configuration is removed, and the update interval will use the default value (60 seconds).

If you have already configured Glances integrations, the previously saved interval option will still be used. To revert to the default update interval, you need to re-add the integration.

You can use the homeassistant.update_entity service in an automation for custom update intervals.

(@engrbm87 - #72748) (documentation)

Groups

Media player groups containing players that provide an invalid media player entity state, will now report a "Unknown" group state.

The list of valid media player states is available in our developer documentation.

(@epenet - #78465) (documentation)

HERE Travel Time

The HERE Travel Time integration now uses the HERE API v8. Travelmode publicTransportTimeTable has been merged into publicTransport. Your configuration will be migrated automatically; no manual interaction is necessary.

(@eifinger - #80892) (documentation)

---

The unit system is no longer controlled by an options setting of the HERE Traveltime integration but uses the built-in custom units configurable per entity.

The distance sensor now uses kilometers as a default and must be manually configured if it was previously using the imperial system.

(@eifinger - #79159) (documentation)

Hikvision

The videoloss event has been removed from the supported list. The event has always been used as a keep-alive for most Hikvision devices, and the library uses it internally. Leaving it enabled as an option causes everything to break if the event is actually processed, so it was removed to eliminate confusion.

Any customized options specified in the YAML configuration for a videoloss event will need to be removed, and videoloss entities will no longer be generated by the integration.

If you used any of these entities in your automations or scripts, you will need to update those to remove the use of these entities.

(@mezz64 - #81173) (documentation)

HomeKit

The HomeKit Air quality PM10 mappings between Home Assistant and HomeKit, have been updated to the latest US AQI standard.

(@stackia - #81217) (documentation)

Logitech Harmony Hub

The PowerOff state of the select entity will be changed to power_off.

If you relied on this state value in your automations or script, you must adjust to this change.

(@bieniu - #77491) (documentation)

Mobile Apps

The events fired when the mobile app scanned a Tag had an incorrect device ID; This has been corrected.

As a result, the evens now contain a different but correct device ID. If you relied on the device ID in your automations, you might need to adjust those with the new device ID.

(@balloob - #82820) (documentation)

Modbus

The name of the mapping keys used for defining HVAC modes in the Modbus climate integration (introduced in 2022.11) has changed. This was needed to fix an issue with the off key, which has a different meaning in YAML.

Instead of:

hvac_mode_register:
  address: ...
  values:
    off: 0
    heat: 1
    cool: 2

You now have to use:

hvac_mode_register:
  address: ...
  values:
    state_off: 0
    state_heat: 1
    state_cool: 2

(@avishorp - #81749) (documentation)

MQTT

YAML configuration of MQTT entities under the platform key (e.g., light), which was deprecated in Home Assistant Core 2022.6, is no longer supported. The configuration must instead be done under the mqtt key.

The legacy MQTT device tracker is no longer supported. See the documentation for the supported MQTT device tracker configuration.

As of this release, you should now use the modern configuration schema for all manually configured MQTT entities. Please note that this does not impact MQTT discovery, for example, Zigbee2MQTT.

(@jbouwh - #82102) (documentation)

---

The encoding configuration option for the MQTT camera set to b64 was previously deprecated and has now become an invalid configuration.

The new image_encoding configuration option is now used to set Base64 encoding. Please use the new image_encoding config parameter (set to b64) instead.

(@jbouwh - #82244) (documentation)

OpenUV

The previously deprecated openuv.update, openuv.update_uv_index, and openuv.update_protection_data services have now be removed.

(@bachya - #81055) (documentation)

Radarr

The previously deprecated YAML configuration of the Radarr integration has been removed.

Radarr 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.

(@tkdrob - #81210) (documentation)

RainMachine

The previously deprecated extra_water_on_hot_days and freeze_protection binary sensors, and freeze_protection_temperature sensor have now been removed.

(@bachya - #81053) (documentation)

Renault

The unit of measurement for the charging power sensor has been corrected. As the unit has changed, it will create a long-term statistics warning that you need to resolve in the statistics developers tools manually.

my.home-assistant.io/redirect/developer_statistics

(@epenet - #81412) (documentation)

You will need to resolve the analytics warning by adjusting the previous unit.

Risco

The bypassed attribute in Risco zones has been removed and replaced with a switch. The matching services have also been removed, and you can bypass and un-bypass a zone using the regular switch services (turn_on and turn_off respectively).

For example, if you had a call to:

service: risco.bypass_zone
target:
  entity_id: binary_sensor.motion_bedroom

You can replace it with:

service: switch.turn_on
target:
  entity_id: switch.motion_bedroom_bypassed

(@OnFreund - #81137) (documentation)

SimpliSafe

The previously deprecated simplisafe.clear_notifications service has now been removed.

(@bachya - #81054) (documentation)

Statistics

The quantiles statistics sensor characteristic has been removed and replaced by the more versatile percentile characteristic.

If you use the quantiles characteristic, you will need to adapt your sensor configuration to recreate identical values with the percentile characteristic.

(@ThomDietrich - #81749) (documentation)

---

The configuration of statistics sensors has changed:

The state_characteristic configuration setting is now mandatory.

The sampling_size configuration setting is now optional and no longer defaults to the arbitrary value 20. You can now define sampling_size, max_age, or both depending on your use case. Existing sensors won't behave differently by the change. However, you might want to check whether your currently defined sensors have a meaningful sampling_size configured or if you wish to remove this setting altogether.

(@ThomDietrich - #81749) (documentation)

Subaru

The Subaru API has changed and no longer returns values required by two sensors:

• External temp
• 12V battery voltage

These sensors have been removed from the Subaru integration.

(@G-Two - #83213) (documentation)

UniFi Network

As new PoE entities were introduced with 2022.11, this release, the old troublesome PoE client implementation that these entities replaced, has been removed. Upgrading will automatically remove the old entities.

Please note that the new PoE entities are disabled by default and represent each PoE-capable port without mapping it to a client.

(@Kane610 - #81749) (documentation)

Farewell to the following

The following integrations are also no longer available as of this release:

• Google Chat has been removed. It relied on the Google Hangouts APIs, which have been shut down, rendering the integration unusable.