Upgrade Path

Home Assistant Core 2023.6.0 → 2023.7.0

4 versions, 12 breaking changes in 1 version, 0 required stops

Version by version, oldest first

2023.6.1 – 2023.6.3: no action items (3 versions)

2023.7.0 2023-07-05

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

Breaking

Home Assistant Container (Docker)

If you use the Home Assistant Container installation method, for example, using Docker, please make sure you are using our official (multi-platform) images.

The correct and preferred image to use for our stable releases is:

  • ghcr.io/home-assistant/home-assistant:stable

Although not the preferred location by the Home Assistant project, the image is also available on DockerHub:

  • homeassistant/home-assistant:stable

The reason for mentioning this in this breaking change section is that we have seen usage of our internal, intermediate, platform build images. These images are not meant for use directly, and using the above listed images is strongly recommended.

As of this release, we no longer publish our intermediate platform images to DockerHub. This means that if you are using these images, you will no longer receive updates. Please use the above-listed images instead.

(@pvizeli - #95236)

Breaking

Bose SoundTouch

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

Bose SoundTouch 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.

(@gjohansson-ST - #94090) (documentation)

Breaking

Conversation

When using the Assist shortcut on iOS, it will now always talk to Home Assistant conversation agent even if the OpenAI or Google LLM conversation integrations are set up.

(@balloob - #95225) (documentation)

Breaking

ESPHome

As an additional security hardening measure, the default for allowing ESPHome devices to make service calls has changed. If you want to permit the ESPHome device to make service calls, it must be enabled in the options flow.

  • For existing devices, calling Home Assistant services continues to be allowed.
  • For newly configured devices, it must now be enabled in the options flow.

(@bdraco - #95143) (documentation)

Breaking

Home Assistant Supervisor

The default name given to backups created with the hassio.full_backup and hassio.partial_backup services is now longer "" but the date and time the backup was initiated (%Y-%m-%d %H:%M:%S, for example, "2023-07-05 13:37:42").

(@ludeeus - #94468) (documentation)

Breaking

Hyperion

The behavior of Hyperion lights has changed:

Turning off the light entity will only clear the priority you have configured during the integration setup. Other Home Assistant independent light sources in Hyperion might still be active and cause light to be emitted. If you want to turn the light off entirely, regardless of active light sources, you can enable the switch.[instance]_led_device entity that acts as a global switch.

External effects that are unrelated to the Hyperion light source (such as USB capture) have been removed from the light entity. To control them, enable the respective disabled-by-default switch entity.

([@Sab44 ] - #80478) (documentation)

Breaking

MQTT

If the initial temperature, min_temp, or max_temp is not set, the default temperature will be converted to the set temperature_unit or system default temperature unit if this is not degrees Celsius.

(@jbouwh - #93965) (documentation)


The behavior of MQTT climate when power_command_topic is set has been changed:

  • The hvac_mode state attribute is no longer optimistically set if power_command_topic is defined and climate.turn_on or climate.turn_off is called.
  • When hvac_mode is changed, payload_on or payload_off messages will not be published on the power_command_topic.

This also means power_command_topic is no longer deprecated.

(@jbouwh - #94832) (documentation)

Breaking

MusicCast

The values for the source attribute have changed. We wanted to show more user friendly values for the source attribute, such as "Net Radio" instead of "net_radio".

If you have any automation depending on the source state attribute of the media player entity, you will have to update these. Calling the select_source service will still be possible using the old source names. (@micha91 - #74954) (documentation)

Breaking

SMHI

The attribute cloudiness has been replaced by the attribute cloud_coverage. Please update any automation or scripts that is using this attribute to use the newly added cloud_coverage attribute.

(@gjohansson-ST - #95096) (documentation)

Breaking

Slack

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

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

(@gjohansson-ST - #94106) (documentation)

Breaking

Xbox

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

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

(@gjohansson-ST - #94094) (documentation)

Breaking

Z-Wave

Fan speed percentage for Honeywell(JE/Jasco) 39358 and Enbrighten(GE/Jasco) 55258 in wall fan controllers are now mapped to levels (low, medium, high).

This may affect scripts or automatons setting fan speeds to specific percentages.

(@jgrieger1 - #92371) (documentation)

Note

Farewell to the following

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

  • SenseME has been removed. Big Ass Fans changed the protocol in a newer firmware in April 2022. The Big Ass Fans integration can be used as a replacement, after updating to the latest firmware. (@bdraco - #94363)

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

Full release notes for 2023.7.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).