Home Assistant Core 2023.8.0 → 2023.9.0
5 versions, 16 breaking changes in 1 version, 0 required stops
Version by version, oldest first
2023.8.1 – 2023.8.4: no action items (4 versions)
2023.9.0 2023-09-06
Quoted from www.home-assistant.io/blog/2023/09/06/release-20239/#backward-incompatible-changes
Breaking
BMW Connected Drive
The "Refresh from cloud" button has been removed. Use the homeassistant.update_entity service with any BMW entity for a full reload instead.
(@rikroe - #97864) (documentation)
Breaking
DoorBird
The doorbird_reset_favorites event is no longer fired when the clear webhook is called. Note: this event was never documented.
(@bdraco - #98585) (documentation)
Breaking
Enphase Envoy
Envoy versions < 3.9 (pre-API) are no longer supported as they require web scraping which is disallowed by ADR-0004.
(@bdraco - #97862) (documentation)
Breaking
ESPHome
To prevent cross-linked devices, replacing an ESPHome device with a different board is no longer allowed. Instead, delete the integration entry and re-add the new device when the mac address of the board changes.
(@bdraco - #98787) (documentation)
Breaking
EZVIZ
Only switches supported by the camera will be created. Non switchable switches have been removed.
(@RenierM26 - #95672) (documentation)
Breaking
Flume
You might get false positives for leak detected and high flow sensors if you have old unread notifications in the Flume app.
Before, the leak detected and high flow sensors would only trigger until you read the notification in the Flume app which was too late for Home Assistant to take any automated action.
Now, they trigger regardless if you have read or not the notification. They will remain active until you delete the notification in the Flume app, similar to the old behavior documented.
(@tronikos - #98560) (documentation)
Breaking
Hive
The previously deprecated service hive.boost_heating has been removed.
Breaking
HTTP / Webserver
Home Assistant can't be put in an iframe anymore by default. If you still want to embed the Home Assistant interface in a frame, you can do so by disabling use_x_frame_options by setting it to false in the http configuration.
(@frenck - #97784) (documentation)
Breaking
Météo-France
The Météo-France weather entities have been updated:
- The
forecaststate attribute is deprecated and will be removed in Home Assistant Core 2024.3, you should instead use theweather.get_forecastservice. - The config entry option to select hourly or daily forecast can no longer be adjusted, but any existing configuration of the forecast period will be respected until Home Assistant Core 2024.3.
- Météo-France now provides a single weather entity which supports both hourly and daily forecast.
(@emontnemery - #98022) (documentation)
Breaking
Mill
Mill has moved to a new IoT solution and released a new API. The unique ID from the old API is no longer available, so all devices will be shown as new devices. Support for the heater fan will be added later.
Breaking
MQTT
MQTT device trackers no longer always update when there is no state change. This means that automations that trigger on a state change no longer are triggered if there is no change.
(@jbouwh - #98838) (documentation)
Breaking
Nextcloud
The CPU load sensor has been replaced, it is not a list of 3 values anymore, but there are now three single sensors for CPU load within last 1, 5, and 15 minutes.
(@mib1185 - #99141) (documentation)
Breaking
Plugwise
The maximum_boiler_temperature sensor entity has been replaced by a number entity, allowing control as well.
(@CoMPaTech - #97203) (documentation)
The additional schema state attributes of the climate entity have been removed. They have beeen previously replaced by a select entity.
(@bouwew - #98153) (documentation)
Breaking
Start.ca
Start.ca limit, usage, and used_remaining sensors will no longer be created when there's no bandwidth cap.
(@emontnemery - #98525) (documentation)
Breaking
Trafikverket Train
All attributes have been converted into their own sensors. The original sensor is now renamed with suffix "Departure time".
Any automation or script depending on these attributes needs to be adjusted to use these new sensors.
Breaking
Z-Wave
The entity naming logic has been updated to be less brittle. As a result, some zwave_js entities that you haven't given a custom name to may be renamed.
Since they are registered in the entity registry, the entity IDs will not change and your automations should therefore not be impacted by the change.
(@raman325 - #98140) (documentation)
With this release, you will need to update your zwave-js-server instance. You must use zwave-js-server 1.31.0 or greater (schema 31).
If you use the Z-Wave JS add-on, you need at least version 0.1.88. If you use the Z-Wave JS UI add-on, you need at least version 1.15.9. If you use the Z-Wave JS UI Docker container, you need at least version 8.23.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.31.0.
(@raman325 - #99250) (documentation)
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).