Upgrade Path

Home Assistant Core 2024.3.0 → 2024.4.0

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

Version by version, oldest first

2024.3.1 – 2024.3.3: no action items (3 versions)

2024.4.0 2024-04-03

Quoted from www.home-assistant.io/blog/2024/04/03/release-20244/#backward-incompatible-changes

Breaking

Python 3.11 support has been removed

Python 3.11 support has previously been deprecated and has now been removed. Home Assistant now requires Python 3.12 to run.

You don’t have to do anything if you are using the Home Assistant Operating System, Home Assistant Container, or Home Assistant Supervised installation method. In those cases, we handle all of this for you. Your system has been using Python 3.12 for quite some time already.

(@frenck - #114220)

Breaking

AEMET OpenData

The AEMET OpenData integration previously created two entities for each configured location: one provided daily weather forecasts and the other hourly forecasts.

The AEMET OpenData integration now only creates a single entity that provides both daily and hourly weather forecasts.

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

Breaking

Dexcom

The trend sensor now uses values that are using snake_case instead of a space in the middle:

  • rising quickly -> rising_quickly
  • rising slightly -> rising_slightly
  • falling slightly -> falling_slightly
  • falling quickly -> falling_quickly

Please update your automations and scripts accordingly.

(@joostlek - #112423) (documentation)

Breaking

ecobee

The non-functional away preset mode has been replaced with the correct away_indefinitely preset mode.

If any automation or script depends on the away preset mode, it needs to be updated.

(@alexsydell - #108636) (documentation)

Breaking

Environment Canada

The Environment Canada integration previously created two entities for each configured location: one provided daily weather forecasts and the other hourly forecasts.

The Environment Canada integration now only creates a single entity that provides both daily and hourly weather forecasts.

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

Breaking

National Weather Service (NWS)

The National Weather Service integration previously created two entities for each configured location: one provided daily weather forecasts and the other hourly forecasts.

The National Weather Service integration now only creates a single entity that provides both daily and hourly weather forecasts.

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

Breaking

Met Éireann

The Met Éireann integration previously created two entities for each configured location: one provided daily weather forecasts and the other hourly forecasts.

The Met Éireann integration now only creates a single entity that provides both daily and hourly weather forecasts.

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

Breaking

Met Office

The Met Office integration previously created two entities for each configured location: one provided daily weather forecasts and the other hourly forecasts.

The Met Office integration now only creates a single entity that provides both daily and hourly weather forecasts.

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

Breaking

Modbus

The Modbus integration does not allow a configuration with the device only (no entities); this will create an issue, and the entry will not be loaded.

For the special cases (like some custom_components) where it is wanted, please add a dummy entity.

(@janiversen - #113516) (documentation)

Breaking

MQTT

Support for brightness is now assumed for mqtt lights with the json schema unless only color modes rgb, rgbw, or rgbww are supported.

For lights which only support color modes rgb, rgbw, or rgbww, the brightness option flag can still be set to false if brightness is not supported. In this case brightness support is emulated in Home Assistant by scaling the RGBx-values.

For all other color modes except ColorMode.ONOFF, it is assumed brightness is supported, and the brightness attribute will be included in the MQTT payload when the brightness attribute is supplied to the light.turn_on service.

(@jbouwh - #111676) (documentation)

Breaking

myUplink

If you have a Nibe SMO 20 in your account, you will notice that some 550 entities are no longer provided by the integration.

You can safely remove these entities as the integration does not use them.

(@astrandb - #113493) (documentation)

Breaking

Waze Travel Time

The options excl_filter and incl_filter now filter for exact matches to street names in the route. Previously, they only filtered on the short description of the route.

(@eifinger - #108613) (documentation)

Breaking

Weather

The previously deprecated forecast attribute of weather entities, has now been removed. Use the weather.get_forecasts service to get the forecast data instead.

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

Note

Farewell to the following

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

  • OpenCV has been removed. The integration has been in a broken state for over a year and currently has no path forward. (@thecode - #113455)

From www.home-assistant.io/blog/2024/04/03/release-20244/#farewell-to-the-following

Full release notes for 2024.4.0

Release notes from github.com/home-assistant/core/releases, and the official release blog, checked 17 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).