Home Assistant Core 2024.10.0 → 2024.11.0
5 versions, 8 breaking changes in 1 version, 0 required stops
Version by version, oldest first
2024.10.1 – 2024.10.4: no action items (4 versions)
2024.11.0 2024-11-06
Quoted from www.home-assistant.io/blog/2024/11/06/release-202411/#backward-incompatible-changes
Breaking
A. O. Smith
A. O. Smith now provides the hot water status as a percentage rather than low, medium, or high. The hot water status entity has been updated accordingly.
(@bdr99 - #127678) (documentation)
Breaking
Google Calendar
Google Calendar events that are declined are now omitted from the calendar.
Breaking
HomeKit
Historically, many integrations implemented doorbells as binary sensors with a device class of occupancy. This design was replaced with the new event entities, which use a purpose-built device class of doorbell.
HomeKit will no longer automatically link binary sensors with device class occupancy as linked doorbell sensors. However, linked doorbell sensors can still be configured manually via YAML.
(@bdraco - #127668) (documentation)
Breaking
Litter-Robot
Previously, Litter-Robot could have an off state. This has now changed to docked, as off isn’t a valid state for vacuum entities.
Breaking
Netatmo
The preset modes of the thermostat have been renamed in order to support translations Schedule, Frost guard, and Manual have been renamed to schedule, frost_guard, and manual.
(@piitaya - #128890) (documentation)
Breaking
Tibber
The tibber.get_prices action has been adjusted to return datetimes as strings instead of raw datetime objects.
Automations or template sensors using this may need to be modified with an as_datetime filter. See our templating documentation for more information on using these filters.
Breaking
Updates
State attributes of update entities have been changed:
- The
in_progressstate attribute is now always abool, never an integer. - A new state attribute
update_percentagehas been added. Theupdate_percentageis a number between 0-100 if an update is in progress and the entity supports reporting progress, orNoneif an update is not in progress or an update is in progress but the entity does not support reporting progress.
Scripts, automations, custom frontend components, etc., which consume the in_progress state attribute of update entities, need to be updated accordingly.
(@emontnemery - #128877) (documentation)
Breaking
WMS WebControl pro
The open/closed state of awnings will be inverted so that the UI visualization and positioning match reality. This means open (100%) now refers to the awning being completely retracted, and closed (0%) now means the awning is fully expanded. This is not in line with industry terminology, but Home Assistant does not yet natively support awnings of type patio.
(@mback2k - #128079) (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).