Upgrade Path

Home Assistant Core 2023.10.0 → 2023.11.0

6 versions, 10 breaking changes in 1 version, 0 required stops

Version by version, oldest first

2023.10.1 – 2023.10.5: no action items (5 versions)

2023.11.0 2023-11-01

Quoted from www.home-assistant.io/blog/2023/11/01/release-202311/#backward-incompatible-changes

Breaking

Demo

In the unlikely event that you are using the demo integration, you will need to ensure that your YAML configuration for demo integration is only enabled via the integration domain key and not via the entity platform configuration. The latter has been removed.

# Example configuration.yaml

# This is correct
demo:

# This no longer works and should be removed
light:
  - platform: demo

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

Breaking

OpenUV

The OpenUV "UV Level" sensor has updated its possible state values so that translations can occur. The new values are:

  • extreme
  • high
  • low
  • moderate
  • very_high

If you previously used the state values of this sensor in your automations, you will need to update them to use the new values.

(@bachya - #101978) (documentation)

Breaking

OpenWeatherMap

The OpenWeatherMap rain and snow sensors now have a different unit of measurement (mm/h instead of mm) and a different device class (precipitation_itensity instead of precipitation).

(@MatteoGheza - #101485) (documentation)

Breaking

Transmission

The option to set a custom polling interval has been removed. If are using custom interval and really need it, you can use the homeassistant.update_entity in an automation to poll at your custom pace. See our documentation on defining a custom polling interval for more information.

(@engrbm87 - #98858) (documentation)

Breaking

Västtrafik

Västtrafik has upgraded all infrastructure for handling external access, including handling user accounts for 3rd party applications.

This means that users of the older infrastructure now need to migrate to use the new environment. Create a new account at https://developer.vasttrafik.se, then create a new application and subscribe to the Planera Resa v4 API.

Next replace your old client identifier and secret in your Home Assistant configuration.

For more information, see this official post from Västtrafik.

(@Miicroo - #102570) (documentation)

Breaking

WeatherFlow

The VOC device class has been removed from the air density sensor, and its unit of measurement has been changed to kg/m³.

(@natekspencer - #101777) (documentation)

Breaking

Withings

The Withings sleep sensors will now show only the data from last night instead of an aggregation of the data since the day before noon.

(@joostlek - #101993) (documentation)

Breaking

World Air Quality Index (WAQI)

The state attributes of the WAQI air quality sensor have been moved to their own sensors. The previous state attributes are now deprecated and will be removed in 2024.5.

If you are using the state attributes of the WAQI air quality sensor, you will need to update your automations to use the new sensors.

(@joostlek - #101217) (documentation)

Breaking

ZHA (King of Fans)

Improved support for King of Fans (Hampton Bay) breaks previous workarounds such as template fans (example) or automations/scripts that set fan speed percentage or preset.

If you have an automation that sets speed, it will now be at one speed higher. If you set the speed at 100% before, it would actually set the speed at 75%, but now it will be 100%. If you have an automation that sets the preset to 'on' to get 100% speed, now the request will fail, and you will have to change the speed to 100% instead.

(@tronikos - #101859) (documentation)

Breaking

Z-Wave

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

  • If you use the Z-Wave JS add-on, you need at least version 0.2.1.
  • If you use the Z-Wave JS UI add-on, you need at least version 2.2.3.
  • If you use the Z-Wave JS UI Docker container, you need at least version 9.2.3.
  • 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.33.0.

(@raman325 - #102790) (documentation)


Basic Command Class values were previously exposed as number entities and were disabled by default. They are now exposed as light entities and are enabled by default.

If you have scripts or automations that use any of these number entities, they should be updated to use the new light entities instead. Any previously created number entities for this Command Class can safely be deleted once you have validated that your scripts and automations are up to date.

(@raman325 - #101438) (documentation)

Note

Farewell to the following

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

  • Eight Sleep has been removed. The API has changed and is no longer accessible, making the integration unusable. (@raman325 - #102669)
  • IMAP email content has been removed. This functionality is now available in the IMAP integration. Users have been assisted to migrate to the new integration in the past months. (@jbouwh - #101233)
  • Shiftr has been removed. Shiftr.io closed its platform and is no longer available. (@stefanroelofs - #102224)

From www.home-assistant.io/blog/2023/11/01/release-202311/#farewell-to-the-following

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