Home Assistant Core 2024.12.0 → 2025.1.0
6 versions, 9 breaking changes in 1 version, 0 required stops
Version by version, oldest first
2024.12.1 – 2024.12.5: no action items (5 versions)
2025.1.0 2025-01-03
Quoted from www.home-assistant.io/blog/2025/01/03/release-20251/#backward-incompatible-changes
Breaking
1-Wire
The unit of measurement has been removed from 1-Wire counters because count is not a unit 😁
(@jrieger - #132076) (documentation)
Breaking
Denon HEOS
Grouping a HEOS media player will now raise an exception if one of the members is not a valid HEOS player. Previously unknown or invalid members would be silently dropped.
(@andrewsayre - #132213) (documentation)
Breaking
devolo Home Control
The integration with devolo Home Control has been updated to remove the option to set the mydevolo URL. This option was used to integrate with the devolo Home Control Cloud for development purposes only. This option is no longer available.
(@Shutgun - #132821) (documentation)
Breaking
FXCOM RFXtrx
The unit of measurement has been removed from FXCOM RFXtrx counters because count is not a unit 😁
(@jrieger - #133108) (documentation)
Breaking
HomeWizard Energy
The unit of measurement for the "Water usage" sensor has been updated from l/min to L/min. This change standardizes the unit to improve consistency across Home Assistant.
Any automations, scripts, or templates that rely on the old unit may need to be adjusted. Long-term statistics will remain intact, but repair issues will be created to ensure the data is updated with the new unit.
(@DCSBL - #132261) (documentation)
Breaking
LIFX
The options color_temp and kelvin are no longer valid arguments for LIFX actions. Please use color_temp_kelvin instead.
(@epenet - #132730) (documentation)
Breaking
Tesla Fleet
The included OAuth application credentials have been removed, as Tesla no longer supports Open Source application registrations and is moving to a pay-per-use model.
Read more about this announcement in this blog post.
(@Bre77 - #132431) (documentation)
Breaking
UniFi Network
The states of "Device State" sensors have been standardized to match Home Assistant core rules and be translatable. This affects the following UniFi sensor states:
Connected, which now becameconnectedPending, which now becamependingFirmware Mismatch, which now becamefirmware_mismatchUpgrading, which now becameupgradingProvisioning, which now becameprovisioningHeartbeat Missed, which now becameheartbeat_missedAdopting, which now becameadoptingDeleting, which now becamedeletingInform Error, which now becameinform_errorAdoption Failed, which now becameadoption_failedIsolated, which now becameisolatedUnknown, which now becameunknown
If you used those states directly in your automations, scripts, or templates; you will need to adjust those to match these changes.
(@bieniu - #131921) (documentation)
Breaking
Zabbix
The integration now uses the official Zabbix Python API. Because of this, the minimum supported Zabbix version is now 5.0. This change drops support for Zabbix 4 and before.
(@kruton - #131674) (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).