Upgrade Path

Home Assistant Core 2023.4.0 → 2023.5.0

7 versions, 15 breaking changes in 1 version, 0 required stops

Version by version, oldest first

2023.4.1 – 2023.4.6: no action items (6 versions)

2023.5.0 2023-05-03

Quoted from www.home-assistant.io/blog/2023/05/03/release-20235/#backward-incompatible-changes

Breaking

Accuweather

The ozone sensors and the ozone state attribute of the weather entity showed incorrect values and are being removed. If you use these values in your automations or scripts, you need to update them.

(@bieniu - #91492) (documentation)

Breaking

Android TV

The "Android TV" integration has been renamed to "Android Debug Bridge".

This rename is because that is what it actually controlled/provided. With the addition of the Android TV Remote integration in this release, we wanted to reduce possible confusion in the future.

(@tronikos - #90657) (documentation)

Breaking

History

All YAML configuration options for the history integration have been removed as they were no longer used by the frontend.

(@bdraco - #90992) (documentation)

Breaking

HomeKit

The min/max target humidities for (de)humidifier device exposed over HomeKit has changed. The HomeKit UI will now show the real relative humidity. When the slider in HomeKit goes above or below the max/min set humidity, it will be set back to the max/min allowed humidity.

(@stackia - #90854) (documentation)


Default HomeKit to listen on all interfaces to match Home Assistant behavior. To limit HomeKit to specific network interfaces, specify an address in configuration.yaml.

(@bdraco - #91520) (documentation)

Breaking

IMAP

The use of imap_content event could break for users that want to parse data from larger email messages from the truncated part. Only the first 2048 bytes of the message body (2 KiB) will be available.

(@jbouwh - #92066) (documentation)

Breaking

Overkiz

The silence option for DynamicShutter has been removed because it caused the cover entity to be non-functional if it did not support silence. This functionality will be reintroduced in a future release.

(@iMicknl - #91354) (documentation)

Breaking

Reolink

For Reolink doorbells, the "Status LED" light entity is replaced by a "Status LED" select entity. The switch off state corresponds to the select Auto, and the switch on state corresponds to the select Auto & always on at night. An additional Stay off state is now available.

(@starkillerOG - #90469) (documentation)

Breaking

Snapcast

  • Muted groups with stream playing will have state idle instead of playing.
  • Connected clients will not have state on anymore but use the same states as groups: idle and playing.
  • Disconnected clients have state standby instead of off because the Snapcast server still accepts commands.

(@luar123 - #77449) (documentation)

Breaking

Synology DSM

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

You may need to update the historically recorded units for these sensors via the statistics page under developer tools.

(@mib1185 - #90633) (documentation)

Breaking

Templates

The ensure_ascii argument for to_json in Jinja templates now defaults to False, allowing us to use a faster JSON encoder by default.

This should not be an issue for most, as JSON parsers broadly accept Unicode input. If you still need to encode Unicode characters inside JSON strings, set ensure_ascii to True explicitly to restore the old behavior.

(@depoll - #91253)

Breaking

UniFi Network

UniFi integration no longer provides both hostname and host_name attributes for a client tracker entity. Only host_name will be provided as an attribute.

(@Kane610 - #91188) (documentation)

Breaking

UniFi Protect

The previous deprecated set_doorbell_message service has been removed. Use the text entity for the UniFi Protect LCD screen instead.

(@AngellusMortis - #91523) (documentation)

Breaking

Universal Devices ISY/IoX

The previously deprecated YAML configuration of the Universal Devices ISY/IoX integration has been removed.

Universal Devices ISY/IoX 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.

(@shbatm - #91575) (documentation)


The built-in percentage unit % is now used for relative humidity and absolute humidity instead of the custom units %RH and %AH, respectively.

(@shbatm - #90863) (documentation)


The following custom ISY994 services have been removed:

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

These services had been previously deprecated in favor of built-in services and number, select, and button entities. Please update your automations and dashboards to use the new entities and/or built-in services if you have not already.

(@shbatm - #91569) (documentation)


Dusk/Dawn nodes on Insteon Motion Sensors now have their states inverted to correctly show "Light detected" during daylight and "No light" when the dusk sensor is active.

This is reversed from previous behavior. If you rely on this sensor in your automations, they must be updated.

(@shbatm - #92035) (documentation)

Breaking

Webhooks

Two new Webhook trigger options have been added that limit how a webhook can trigger an automation. A new _allowed_methods_ option can be used to control which HTTP request methods can activate the trigger (GET, HEAD, POST, and PUT). And the local_only option is used to allow devices outside your local network to activate the trigger.

Previously all webhook triggers could be activated by HEAD, POST, and PUT methods from any device (local or on the internet). With the new options, only POST and PUT are enabled by default.

In Home Assistant Core 2023.7, any webhook trigger that does not set local_only to false can only be activated by devices on the same network as Home Assistant.

Click the gear/cog icon beside the Webhook ID to update your webhook triggers. Then select an appropriate value for Only accessible from the local network. It is necessary to deselect the option for the Save button to appear. Then reselect the option if it should be enabled. This will make the repair warning go away.

[image: Screenshot shoting webhook trigger options]

See the webhook trigger documentation for a description of the new options. And please review the new Webhook Security section for best practices when using webhook triggers.

(@esev - #66494) (documentation)

Breaking

Z-Wave

With this release, you will need to update your zwave-js-server instance. You must use zwave-js-server 1.28.0 or greater (schema 28).

  • If you use the Z-Wave JS add-on, you need at least version 0.1.79.
  • If you use the Z-Wave JS UI add-on, you need at least version 1.11.2.
  • If you use the Z-Wave JS UI Docker container, you need at least version 8.14.2.
  • If you run your own Docker container or some other installation method, you will need to update your zwave-js-server instance to at least 1.28.0.

(@raman325 - #91989) (documentation)

Note

Farewell to the following

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

From www.home-assistant.io/blog/2023/05/03/release-20235/#farewell-to-the-following

Full release notes for 2023.5.0

Release notes from github.com/home-assistant/core/releases, and the official release blog, checked 18 hours ago. Only text the vendor marks as breaking, or puts in a warning/caution/important note, is shown; read the full notes for anything else. Home Assistant lists its breaking changes in the “Backward-incompatible changes” section of each monthly release post on home-assistant.io (2020.12 onward). Each entry of that section is quoted as “Breaking” on the x.y.0 release, under the integration name the post gives it. The post’s “Farewell to the following” section (integrations removed in that release, 2020.12–2024.5) is quoted whole as “Note”. The post's separate section for custom integration developers is not quoted. Patch releases are listed but their notes (lists of fixes) are not quoted. Versions come from PyPI (package homeassistant).