Upgrade Path

Home Assistant Core 2026.1.0 → 2026.2.0

4 versions, 5 breaking changes in 1 version, 0 required stops

Version by version, oldest first

2026.1.1 – 2026.1.3: no action items (3 versions)

2026.2.0 2026-02-04

Quoted from www.home-assistant.io/blog/2026/02/04/release-20262/#backward-incompatible-changes

Breaking

Group

The behavior of sensor groups has changed:

  • A sensor group is now unavailable if all group members are either unavailable or missing (meaning they are not in the state machine).
  • When the group is not considered unavailable and the configuration variable ignore_non_numeric is set to False (the default), the group state is calculated according to the configured type only if all group members are in the state machine and have a numeric state. If not, the group state will be unknown.

(@emontnemery - #152167) (group documentation)

Breaking

Sentry

Self-hosted Sentry users only: This upgrade requires Sentry server version 20.6.0 or later (released June 2020) due to the SDK's use of the /envelope API endpoint. Users running older self-hosted Sentry instances must upgrade their server before updating Home Assistant.

Home Assistant users using sentry.io are not affected.

(@vaind - #159415) (sentry documentation)

Breaking

Tractive

The following sensors have been removed because they are no longer supported by the Tractive API:

  • activity
  • calories burned
  • sleep

If you use these entities in your automations or scripts, you must update them.

(@bieniu - #160089) (tractive documentation)

Breaking

Tuya

Duplicate HVACMode have been converted to presets. You may need to adjust service calls from set_hvac_mode to set_preset_mode in your automations or scripts.

(@epenet - #160918) (tuya documentation)

Breaking

VeSync

The advanced_sleep preset mode is now replaced by sleep. If you have been using advanced_sleep, in your automations or scripts, you must update them to use sleep instead.

(@cdnninja - #160573) (vesync documentation)

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