Upgrade Path

Home Assistant Core 2023.2.0 → 2023.3.0

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

Version by version, oldest first

2023.2.1 – 2023.2.5: no action items (5 versions)

2023.3.0 2023-03-01

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

Breaking

Assist / Conversation

Previously, all entities and areas were exposed to Assist's default agent. This is now restricted to entities of the following domains:

  • climate
  • cover
  • fan
  • humidifier
  • light
  • lock
  • scene
  • script
  • sensor
  • switch
  • vacuum
  • water_heater

Only areas with exposed entities will be exposed themselves. In the future, this will be customizable through the frontend.

(@synesthesiam - #88274) (documentation)

Breaking

Atmospheric pressure device triggers

A bug with the atmospheric pressure sensor device triggers has been corrected. Automations using such device triggers will need to be adjusted/reconfigured.

(@epenet - [#88320]) (documentation)

Breaking

ecobee

The aux heat toggle will now show as enabled when the device is in "aux heat only" mode instead of only when it is running.

(@Lash-L - #86100) (documentation)

Breaking

Fibaro

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

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

(@rappenze - #87939) (documentation)

Breaking

GoodWe Inverter

Inverter "Operation Mode" select values were changed to snake_case and localized.

  • "General mode" -> general
  • "Off grid mode" -> off_grid
  • "Backup mode" -> backup
  • "Eco mode" -> eco
  • "Peak shaving" -> peak_shaving
  • "Eco charge mode" -> eco_charge
  • "Eco discharge mode" -> eco_discharge

If you used these select values in your automations or scripts, you will need to adjust those to match this change.

(@mletenay - #86901) (documentation)

Breaking

HomeKit

VOC mappings in the HomeKit integration have been improved to use the IAQ guidelines for Europe released by the WHO (World Health Organization).

HomeKitPrevious VOC µg/m3New VOC µg/m3
Excellent<= 24<= 250
Good<= 48<= 500
Fair<= 64<= 1000
Inferior<= 96<= 3000
Poor> 96> 3000

Reference: Sensirion_Gas_Sensors_SGP3x_TVOC_Concept.pdf

(@emanuelst - #87663) (documentation)

Breaking

Matter

With this release, you will need to update your Matter Server instance. You must use python-matter-server 3.0.0 or greater (schema 2).

  • If you use the Matter Server add-on, you need to have at least version 4.0.0.
  • If you run your own Docker container, or some other installation method, you will need to update your python-matter-server instance to at least 3.0.0.

(@marcelveldt - #88607) (documentation)

Breaking

MQTT

The behavior for receiving values on sensors that expect numeric* values has changed.

  • A 'None' value or a value rendered to 'None' will set such a sensor to an unknown state.
  • Empty values on such sensors ('') are ignored and will not affect the state of the sensor.

Integrations need to be corrected to send the correct values if an update is published and no valid update value is available for the sensor.

  • Other sensors that do not expect a numeric value will still accept an empty string as a value.

* Sensors expect numeric values if at least one of the following applies:

  • A device_class is set but is not a date, timestamp, enum, or any custom device class.
  • A state_class is set.
  • A unit_of_measurement is set.
  • A suggested_display_precision is set.

(@jbouwh - #87004) (documentation)

Breaking

Plugwise

The unit of measurement for the P1 gas consumed interval sensor is changed from m³ to m³/h. Go to Developer Option --> Statistics for the options on how to handle this change in your existing installation.

(@bouwew - #87449) (documentation)

Breaking

Profiler

The profiler.memory service is unavailable when using Python 3.11, due to an incompatibility with a needed dependency for this service. It will return when the used guppy3 package becomes available with Python 3.11 compatibility.

(@bdraco - #88136) (documentation)

Breaking

Template: Covers

Template covers using optimistic: false without value_template nor position_template still updated state optimistically. The integration now respects the optimistic setting of false. If you want to keep the previous behavior, you must set the optimistic value to true, or remove the optimistic declaration.

(@ylemoigne - #87925) (documentation)

Breaking

Trafikverket Weather

The unit of measurement was incorrectly set to mm while the API is returning mm/h. The unit of measurement and device class have now been corrected.

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

Breaking

Todoist

Labels used by custom projects for filtering are now case-sensitive.

Previously the labels were automatically lower-cased by the integration, but in Todoist a label like Test and test are considered unique. Because of that labels will now be case sensitive in your configuration.

(@boralyl - #87904) (documentation)

Breaking

UniFi Protect

The event_id and event_score state attributes are now excluded from being recorded in the database. They remain available for use in automations and scripts.

(@bdraco - #88387) (documentation)


The previously deprecated "Detected Object" sensor has been removed.

The sensor was removed because if multiple objects are detected at once (very common for package detection), Home Assistant could not be automated using the second detected object. The sensor has been split out from the single Detected Object sensor into multiple binary issues for each detection type.

(@bdraco - #85656) (documentation)

Breaking

Wiffi

The Wiffi unit of illuminance lux has been adjusted to the standard unit Home Assistant uses lx.

(@mampfes - #87377) (documentation)

Breaking

Z-Wave

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

  • If you use the Z-Wave JS add-on, you need at least version 0.1.76.
  • If you use the Z-Wave JS UI add-on, you need at least version 1.6.3.
  • If you use the Z-Wave JS UI Docker container, you need at least version 8.8.6.
  • 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.26.0.

(@raman325 - #88520) (documentation)

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