Home Assistant Core 2025.9.0 → 2026.9.4

Targeting labels in automations and scripts

Configuration and diagnostic entities with a label assigned to them will now be targeted/affected by service actions targeting that label. Previously, those entity categories were ignored on service action calls targeting labels.

If you have an automation or script with an action targeting a label, make sure that only entities that should be affected have that label assigned, even if they are config or diagnostic entities.

(@abmantis - #149309) (labels docs)

HERE Travel Time

HERE deprecated the previous free tier. The new Base Plan has 5000 free requests per month. The automatic update interval of the HERE Travel Time integration changed from 5 minutes to 30 minutes, so one route can be supported without costs.

(@eifinger - #147222) (here_travel_time docs)

Home Connect

The Home Connect Alarm clock entity has been removed from the time platform, please use the number entity instead.

(@Diegorro98 - #152188) (home_connect docs)

Shelly

Removed previously deprecated extra attributes, please review your automations.

Shelly Gas:

• The Detected attribute of the Gas entity has been removed, the Gas detected entity should be used instead.
• The Self test attribute of the Operation entity has been removed, the Self test entity should be used instead.

Shelly Air:

• The Operational hours of the Lamp Life entity has been removed, if you still want that info please use a template entity.

(@chemelli74 - #140386) (shelly docs)

Slide Local

The effect of the property "invert position" is extended from the position itself to the status (open or closed). With this adjustment, it is no longer necessary to use cover templates to invert the position to correct the status. If you have covers with inverted position and are using the state in automations, you must adjust the automations accordingly.

(@dontinelli - #150418) (slide_local docs)

SmartThings

The windFree preset mode for the air conditioner has been renamed to wind_free to allow translation to happen. Please adapt automations accordingly.

(@joostlek - #152833) (smartthings docs)

Tibber

Switch Tibber electricity pricing to 15-minute intervals.

• The tibber.get_prices action now returns 15-minute data instead of hourly.
• The price_level attribute is removed and no longer supported.
• The intraday_price_ranking attribute is now scaled to (0,1) to better support 15-minute prices.

(@Danielhiversen - #151881) (tibber docs)

Zabbix

We removed official support for Zabbix 5.0 from the integration. While this does not directly break connections to Zabbix 5.0, future updates will not check for compatibility with this version. Note that Zabbix 5 LTS left its support window in May of 2025.

(@nolsto - #149450) (zabbix docs)

ZHA

Removes the extra ZHA specific cover entity attributes, their values were no longer populated.

• target_lift_position
• target_tilt_position

(@jeverley - #142534) (zha docs)

ZhongHong

ZhongHong's climate entities set_fan_mode action behavior has changed.

The fan mode values are now converted to lowercase instead of uppercase to ensure compliance with the standard convention.

If you have automations relying on uppercase fan mode values, you will need to update them to use lowercase values instead.

(@Blear - #151559) (zhong_hong docs)

Set assumed state to group if at least one child has assumed state

Previously, the group’s assumed state was always false, regardless of the state of its child entities.

This has now changed:

The group will now have an assumed state of true if at least one child entity has an assumed state. This makes the group's assumed state reflect the uncertainty of its children more accurately. These domains have been added: switch, fan, light, and cover.

(@piitaya - #154163) (group docs)

Asuswrt

The last_time_reachable attribute has been removed from the asuswrt device tracker. Use the last_changed attribute instead in your automations.

(@ollo69 - #154219) (asuswrt docs)

LG webOS TV

The state of LG webOS TV media player entities that do not have an automation trigger to turn on the device will be set to unavailable instead of off.

(@thecode - #155164) (webostv docs)

Mealie

The mealie integration now requires Mealie version 2 or later.

Mealie version 1 is no longer supported. Version 2 was released in October 2024, so over a year ago. Given the differences between versions 1 and 2, we are no longer able to support or test backward compatibility with version 1.

(@andrew-codechimp - #153203) (mealie docs)

Motion Blinds

The tilt position of motion_blinds devices has been corrected to align with the Home Assistant standards. The new tilt position will be: 0 = closed/covering the window opening, 100 = open/letting light through. The previous tilt position can be converted to the new tilt position as follows:

• new = 100 - old
• current_tilt_position = 100 -> 0
• current_tilt_position = 75 -> 25
• current_tilt_position = 50 -> 50
• current_tilt_position = 25 -> 75
• current_tilt_position = 0 -> 100
• open_cover_tilt -> close_cover_tilt
• close_cover_tilt -> open_cover_tilt

Any automations concerning Motion Blinds devices that use the current_tilt_position attribute or use tilt open/close will need to be adjusted.

(@starkillerOG - #149777) (motion_blinds docs)

Mobile app

The mobile_app integration, which supports the iPhone and Android companion apps, now handles zone-only updates better. When your companion app sends just the zone name (not the exact coordinates), the device tracker will show the zone's friendly name.

The person entity now shows the zone's friendly name (not its object ID) for custom zones. This might break existing automations that trigger on a person's state.

As an example, if you have a zone named zone.kids_school with the friendly name School:

• Before this change, the state of the corresponding person and device_tracker entities would be kids_school when the "Location Sent" in the companion app was set to send "Zone Name Only" and School when it was set to "Exact".
• After this change, the state of the corresponding person and device_tracker entities will be School for both the "Location Sent" settings in the companion app.

(@Ashus - #149453) (mobile_app docs)

Nederlandse Spoorwegen

The Nederlandse Spoorwegen entity is now displayed as a timestamp entity, rather than a string. Please adapt your automations and scripts.

(@joostlek - #154011) (nederlandse_spoorwegen docs)

ONVIF

The Speed parameter in the ONVIF GoToPreset action is now optional.

The default of 0.5 is no longer set. If you want to restore the previous behavior you have to set speed to 0.5 in your action.

(@carlos-sarmiento - #149636) (onvif docs)

OralB

In the OralB integration, states and attributes have changed.

In multiple places, spaces have been replaced with underscores:

• Toothbrush state:

• flight menu → flight_menu
• selection menu → selection_menu
• final test → final_test
• pcb test → pcb_test

• Brushing mode:

• daily clean → daily_clean
• gum care → gum_care
• tongue cleaning → tongue_cleaning
• super sensitive → super_sensitive
• deep clean → deep_clean

• Pressure:

• power button pressed → power_button_pressed
• button pressed → button_pressed

• Sector:

• no sector → no_sector
• sector 1 → sector_1
• sector 2 → sector_2
• sector 3 → sector_3
• sector 4 → sector_4

Automations should be updated to use the new states and attributes.

(@tr4nt0r - #153605) (oralb docs)

Renault

The discovery of Renault functionality was previously based on assumptions that may have created invalid and non-functional entities. These will no longer be created.

(@epenet - #154137) (renault docs)

Traccar Server

The Traccar integration has been updated to use a more secure API Token for authentication. This is a required, one-time breaking change to align with Traccar's security recommendations and ensure the integration continues to work.

This release migrates the integration away from the older username/password method, ensuring continued stability and security for all users while also allowing users with SSO-based setups to use the integration.

When you update Home Assistant, the existing Traccar integration will need to be re-authenticated:

1. Generate an API Token on your Traccar server (you'll find this option in your Traccar server's user settings).
2. Go to Settings > Devices & services > Traccar Server.
3. Click "Reconfigure" and enter your new API Token when prompted.

Once you've done this, your Traccar devices and entities will work exactly as they did before.

(@pantherale0 - #155297) (traccar_server docs)

Xbox

The Account tier and Gold tenure sensors have been retired, as they no longer receive updates following the transition from Xbox Live Gold to Xbox Game Pass. Additionally, the In party and In multiplayer binary sensors have been removed, since they’ve been non-functional for quite some time.

(@tr4nt0r - #154891) (xbox docs)

Core and Supervised installation methods, and 32-bit systems

After a 6-month deprecation period, support for the Home Assistant Core and Home Assistant Supervised installation methods, as well as all 32-bit system architectures (i386, armhf, and armv7), has now been fully removed.

These installation methods and architectures will no longer receive updates, including security updates. If you are still using one of these installation methods or architectures, please migrate to a supported installation method and architecture as soon as possible to continue receiving updates and support.

For more information on this change, read the Deprecating Core and Supervised installation methods, and 32-bit systems blog post.

Hive

Hive has removed support for their security products. We have removed the alarm control panel from the integration, as the Hive APIs no longer support these products.

(@KJonline - #156184) (hive docs)

Templates

The issues() templating method used to return all issues, including fixed issues. From now on, only active issues are returned.

(@jbouwh - #156274)

go2rtc

It is now required to set a username and password when enabling the debug UI.

(@edenhaus - #157008) (go2rtc docs)

UniFi Protect

The legacy license plate event sensor has been removed from the UniFi Protect integration, as it no longer functions with Protect 6 and newer. The UniFi Protect integration has not been compatible with Protect versions older than 6 for quite some time.

This sensor has been replaced with a new Vehicle Detection Event entity that provides significantly more functionality, including license plate recognition, vehicle type detection, color detection, and confidence scores. The new event entity fires with a 3-second delay to ensure optimal thumbnail and LPR data quality.

For more information and automation examples, see the Vehicle Detection Event documentation.

(@RaHehl - #157196, #157203) (unifiprotect documentation)

Xbox

• The Xbox media browser has been completely overhauled to support multiple accounts and introduce a range of other improvements. As part of this update, the format of the media-source identifiers has been changed as well.

• The following and followers sensors introduced in the last release previously included friends in their counts. After a recent API update, friends are no longer included.

(@tr4nt0r - #155925) (@tr4nt0r - #155536) (xbox docs)

Coolmaster

The climate entities provided by the Coolmaster integration now use medium for the medium fan mode; before this change, it was med. If your automations are using med when setting or querying the fan speed, you'll have to change it to medium.

(@tan-lawrence - #157253) (coolmaster docs)

Tailscale

The "Supports hairpinning" binary sensor has been removed from the Tailscale integration. According to the official Tailscale API documentation, this information is no longer tracked and will always return null.

(@CraigCallender - #156728) (tailscale docs)

UniFi Protect

Select entity state values have been changed from their original mixed-case format to snake_case format with proper translations. This improves consistency and enables proper localization support.

Affected select entities include: chime type, recording mode, infrared mode, status light mode, HDR mode, doorbell text, LCD message, and others.

Example changes:

• Chime type: Mechanical → mechanical, Digital → digital
• Recording mode: Always → always, Detections → detections, Never → never
• Infrared mode: Auto → auto, On → on, AutoNoLEDsOn → auto_no_leds_on
• Status light mode: On → on, Off → off, OnWhenDark → on_when_dark
• HDR mode: Auto → auto, On → on, Off → off

If you have automations, scripts, or templates that check or set the state of UniFi Protect select entities, you need to update them to use the new snake_case values. The UI will continue to display properly translated, human-readable text.

(@RaHehl - #159284) (unifiprotect docs)

Telegram bot

Allowing extra/unused parameters has been removed from the action for Telegram bot. Only users who have used undefined parameters for Telegram bot actions are affected. If you are affected, remove such parameters from your automations and scripts. Supported parameters can be found in the Telegram bot notification actions documentation.

(@hanwg - #158886) (telegram_bot docs)

VeSync

The advancedSleep fan mode has been changed to advanced_sleep. If you have automations or scripts using this fan mode, please update them accordingly.

(@cdnninja - #158956) (vesync docs)

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)

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)

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)

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)

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)

BSB-Lan

The water heater operation mode state on has been changed to performance for the BSB-Lan water heater. If you use this state in your automations or scripts, you will need to update them to use the new state value.

(@liudger - #160256) (BSB-Lan documentation)

Container image

Home Assistant container images are now compressed with zstd instead of gzip. This change is supported on Docker 23.0.0 and later, and containerd 1.5.0 and later, so it is not expected to break installations that meet these minimum versions. If your environment uses an older Docker or containerd version, make sure your container runtime supports zstd before updating.

(@duhow - #160665)

LIFX

Passing the color_temp parameter (in mireds) to the lifx.effect_pulse action is no longer allowed. Use the color_temp_kelvin parameter instead.

(@Djelibeybi - #161848) (LIFX documentation)

Lights

Using color_temp (in mireds) to set a light's color temperature is no longer supported. Use color_temp_kelvin instead.

Additionally, the color_temp, kelvin, min_mireds, and max_mireds light entity state attributes have been removed. Use color_temp_kelvin, min_color_temp_kelvin, and max_color_temp_kelvin instead.

(@emontnemery - #161777) (light documentation)

Satel Integra

Binary sensors and switches now have an initial state of unknown while the alarm panel is still reporting all states during startup. Previously, the default state was off, which was incorrect, as no data had been received from the panel yet.

The chance that you are impacted is low, as most states are reported before Home Assistant fully finishes setup; but this might occur on larger installations and slower connections.

(@Tommatheussen - #158533) (Satel Integra documentation)

Snapcast

Media player entities for Snapcast groups have been removed. Additionally, the Snapcast-specific grouping actions have been removed. If you use these entities or actions in your automations or scripts, you will need to update them.

(@luar123 - #160945) (Snapcast documentation)

StarLine

The ignition and autostart state attributes of the engine switch have been removed. Two new binary sensors have been introduced to replace them. If you reference these attributes in your automations or scripts, update them to use the new binary sensor entities instead.

(@epenet - #163289) (StarLine documentation)

Tado

Mobile device tracking has been removed from the Tado integration. Mobile devices and their associated device tracker entities are no longer available. This change resolves re-authentication issues and reduces unnecessary load on the Tado API.

(@erwindouna - #160881) (Tado documentation)

Template

The behavior of template fans has changed:

• A template fan's state will be unavailable if the state template encounters a syntax error. Previously, a template error would show the fan's state as off.
• The percentage attribute will be None if the percentage template encounters a syntax error. Previously, it would be 0.
• Template fans can now have the unknown state. A state template that returns None will render the entity as unknown instead of off.

(@Petro31 - #162328) (Template documentation)

Z-Wave

Percentage speeds reported by Z-Wave fans have been corrected to align with other integrations. As a result, values may differ slightly. For example, a value previously reported as 67% may now appear as 66%. If you have automations that trigger on exact percentage values, you may need to adjust them.

(@arturpragacz - #163093) (Z-Wave documentation)

JVC Projector

The Picture Mode and HDR Processing entities have been migrated from the sensor domain to the select domain, because they represent selectable settings rather than read-only values.

New entities:

• select.jvc_projector_picture_mode
• select.jvc_projector_hdr_processing

The legacy sensor entities are now deprecated. If a deprecated sensor is disabled and not referenced by automations or scripts, Home Assistant will remove it from the entity registry. If usage is detected, Home Assistant keeps it and shows a repair issue to help you migrate. Update your automations, scripts, dashboards, and templates to use the new select entities.

(@SteveEasley - #165194) (JVC Projector documentation)

Litter-Robot

The deprecated night light mode switch entity for Litter-Robot 4 devices has been removed. This switch was replaced by a select entity in Home Assistant 2025.10. If you still use the old switch entity in your automations or scripts, update them to use the select entity instead.

(@natekspencer - #165636) (Litter-Robot documentation)

Motion Blinds

On devices that support tilt but do not report a tilt position, the tilt open and tilt close operations now send jog up and jog down commands instead of setting the tilt angle to 0° or 180°. Setting an absolute tilt position usually didn't work on these devices anyway, and jog commands provide a meaningful small step in the intended direction.

If you have automations that rely on the previous tilt behavior for these devices, you may need to adjust them.

(@tobiaswaldvogel - #164694) (Motion Blinds documentation)

MQTT

Support for the object_id option has been removed after 6 months of deprecation. This option was used to suggest the entity ID for an MQTT entity and has been replaced by the default_entity_id configuration option.

If you used object_id in your MQTT YAML configuration, you were previously asked via a repair flow to update your configuration. If object_id is still part of a discovery message, the option will simply be ignored and will not break discovery.

(@jbouwh - #164460) (MQTT documentation)

pyLoad

pyLoad 0.4.x is now deprecated, and you should switch to pyLoad-ng 0.5.0. pyLoad-ng introduced a new API, and support for the old API has been dropped.

(@tr4nt0r - #164495) (pyLoad documentation)

Roth Touchline

The preset mode names for the Roth Touchline climate entities have been updated to use standard Home Assistant preset names, making them translatable. If you have automations or scripts that reference the old preset mode names, update them to use the new names:

• Normal → none
• Night → sleep
• Holiday → away
• Pro 1 → program_1
• Pro 2 → program_2
• Pro 3 → program_3

(@joostlek - #166390) (Roth Touchline documentation)

Tuya

Previously deprecated switch entities used to control valves have been removed. Use the valve entities instead. If you have automations or scripts that reference these switch entities, update them to use the corresponding valve entities.

(@epenet - #164657) (Tuya documentation)

Z-Wave

The Z-Wave Installer panel has been removed. This panel was hidden and required an undocumented YAML configuration to enable. The same functionality is now natively available through Z-Wave JS UI in the Z-Wave app.

(@AlCalzone - #165388) (Z-Wave documentation)

Purpose-specific triggers and conditions

When we first introduced purpose-specific triggers and conditions, we added separate ones for Person entities and Device Tracker entities. Since then, we've decided to take a more ergonomic, cross-domain approach instead.

As a result, the entered home and left home triggers, and the is home and is not home conditions, have been removed from Person and Device Tracker. Replacements that work across both will land in an upcoming release.

If you have automations that use these triggers or conditions on a person or device tracker, switch them back to a regular state trigger or state condition (for example, state changed to home) until the cross-domain replacements arrive.

(@emontnemery - #168406)

Gardena Bluetooth

The "finish watering" value in the Gardena Bluetooth integration has been moved from a binary sensor to a regular sensor that exposes the timestamp of when watering is expected to finish. This makes the value far more useful in dashboards and automations.

If you have automations, scripts, or dashboards that reference the previous binary sensor entity, update them to use the new sensor entity instead.

(@elupus - #169476) (Gardena Bluetooth documentation)

pilight

The pilight integration has been disabled because the underlying pilight library relies on setuptools.pkg_resources, which is no longer available in setuptools 82.0.0 and later.

If the library is updated to remove the setuptools.pkg_resources dependency, or replaced with a maintained alternative that does so, the integration can be activated again. Community contributions to make this happen are very welcome.

(@epenet - #167760) (pilight documentation)

Ring

The Ring doorbell event entity now emits the standardized ring event type instead of the legacy ding. This change aligns Ring with the new doorbell event standard, so the entity can be used seamlessly with the new purpose-specific automation triggers and conditions.

If you have automations that listen for the ding event type from your Ring doorbell, update them to use ring instead.

(@abmantis - #167728) (Ring documentation)

Supervisor

Previously, all actions registered by the Supervisor integration (such as hassio.addon_start, hassio.backup_partial, and hassio.host_reboot) only logged an error on failure, and your script or automation would continue running regardless of whether the action succeeded.

These actions now properly raise on failure, which means your automation or script will stop unless continue_on_error is set to true. If you rely on the previous behavior, add continue_on_error: true to those action steps.

(@mdegat01 - #166558) (Supervisor documentation)

Webhook

The local_only option on webhooks must now be a proper boolean (true or false). Previously, other truthy values like 1 or "yes" were silently accepted. This brings the option in line with the rest of Home Assistant.

If you have webhooks configured in YAML with non-boolean local_only values, update them to use true or false.

(@edenhaus - #169296) (Webhook documentation)

Purpose-specific triggers (Labs)

The behavior options for the Labs purpose-specific triggers have been renamed to better match what they do: any is now each, and last is now all. The default is now each.

If you have automations that use these triggers from the Labs preview at Settings > System > Labs, open them in the automation editor and re-pick the behavior option. Any YAML you wrote against the old keys needs to be updated to the new names.

(@emontnemery - #172348)

Bluetooth

The default Bluetooth scanning mode has changed to Auto, which dynamically switches between active and passive scanning depending on what is happening. This saves around 95-96% of the battery used for Bluetooth scanning while keeping the same functionality for most setups.

If you run into issues after the upgrade, you can switch your Bluetooth adapter back to Active scanning. Go to Settings > Devices & services, open the Bluetooth integration, and select Configure on your adapter to change the scanning mode.

(@bdraco - #171985) (Bluetooth documentation)

Certificate Expiry

The error attribute on the certificate expiry sensor now returns a proper None value instead of the string "None" when there is no error.

If you use this attribute in templates, update your comparisons from == "None" to is none.

(@TomFilsell - #170878) (Certificate Expiry documentation)

ESPHome

The default Bluetooth proxy scanning mode for ESPHome devices is now Auto. Devices that were previously set to Active are automatically migrated to Auto, while devices set to Passive keep their setting.

If you need Active scanning for a specific device, change it back in the device options under Settings > Devices & services.

(@bdraco - #171996) (ESPHome documentation)

HDMI-CEC

Calling the turn_off action on HDMI-CEC switch or media player entities now sends the standard CEC standby command instead of a vendor-specific power-off command. This works more reliably across devices from different manufacturers.

If you relied on the previous behavior, you can send the original command using the hdmi_cec.send_command action with keypress 0x44 followed by 0x6c.

(@pattyland - #170206) (HDMI-CEC documentation)

IronOS

The uptime sensor for IronOS soldering irons has changed from a duration sensor (reporting seconds) to a timestamp sensor that reports when the device was started.

Update any automations or dashboards that read this sensor to work with the new timestamp format.

(@tr4nt0r - #169699) (IronOS documentation)

ONVIF

When you call the onvif.ptz action with continuous_duration: 0, the integration no longer sends a Stop command after the ContinuousMove. This lets you start a continuous movement and stop it later with a separate call.

If your automations rely on the camera stopping automatically, set continuous_duration to the desired duration in seconds.

(@yoxcu - #163173) (ONVIF documentation)

Shelly

Shelly devices used as Bluetooth scanners now support the new Auto scanning mode. Existing devices set to Active are automatically migrated to Auto for better battery and performance.

You can change the scanning mode back in the device options under Settings > Devices & services.

(@bdraco - #172008) (Shelly documentation)

SmartThings

The source attribute on SmartThings media players is now normalized to standard Home Assistant values. For example, D.IN is now reported as digital_input and BT as bluetooth.

If you use the source attribute in automations, dashboards, or templates, update them to match the new values.

(@felipecrs - #160034) (SmartThings documentation)

Template entities

The legacy template platform syntax under the individual platform keys has been removed. This syntax was deprecated in Home Assistant 2025.12 and has now reached the end of its 6-month deprecation period.

This affects the following platforms:

• alarm_control_panel
• binary_sensor
• cover
• fan
• light
• lock
• sensor
• switch
• vacuum
• weather

Move your template entities to the modern template: syntax. A step-by-step migration guide is available in the Removal of legacy template entities forum thread.

(@Petro31 - #169608, #169610, #169611, #169613, #169615, #169725, #169728, #169730, #169732, #169734) (Template documentation)

Tuya

The unit of measurement provided by the Tuya API now takes precedence over the default unit assigned by Home Assistant. This makes the reported value match what the Tuya app shows.

If your device reports an invalid or unexpected unit, please submit a bug report with the device details and the unit it reports and adjust it accordingly.

(@epenet - #170338) (Tuya documentation)

Velux

The deprecated velux.reboot_gateway action has been removed. Use the reboot button entity on your Velux gateway instead.

(@wollew - #169796) (Velux documentation)

Purpose-specific triggers and conditions

Several entity triggers and conditions, part of the new purpose-specific triggers and conditions, have been renamed so their keys are consistent across all domains. The old keys no longer work.

The following triggers changed:

• battery.low is now battery.became_low
• battery.not_low is now battery.no_longer_low
• lawn_mower.docked is now lawn_mower.returned_to_dock
• schedule.turned_off is now schedule.block_ended
• schedule.turned_on is now schedule.block_started
• timer.time_remaining is now timer.remaining_time_reached
• update.update_became_available is now update.became_available
• vacuum.docked is now vacuum.returned_to_dock

The following conditions changed:

• climate.target_humidity is now climate.is_target_humidity
• climate.target_temperature is now climate.is_target_temperature

If an automation or script uses one of these, it will stop working until updated. To fix it, open the affected automation or script, re-select the trigger or condition (it now appears under its new name), and save. If you edit in YAML, replace the old key with the new one from the list above.

(@frenck - #174463)

BSB-LAN

The BSB-LAN integration has reduced its support for the older version 1 JSON API. If your BSB-LAN device runs very old firmware that only speaks the version 1 API, update it to firmware that supports the version 2 API to keep everything working.

A repair notification will let you know if your device is affected.

(@liudger - #172843) (BSB-LAN documentation)

iCloud

The battery_level attribute has been removed from iCloud device tracker entities. Use the dedicated battery sensor in your automations and scripts instead.

(@some-random-climber - #174117) (iCloud documentation)

Person

Person entities no longer report the latitude and longitude of the home zone when their location comes from a presence scanner associated with the home zone.

If you have automations or scripts that check the coordinates of a person, adjust them. To check whether a person is in a specific zone, use the new in_zones state attribute instead.

(@emontnemery - #173042) (Person documentation)

Rabbit Air

The Rabbit Air fan preset mode values changed from title case to lowercase to match Home Assistant's state convention: Auto is now auto, Manual is now manual, and Pollen is now pollen. The user-facing labels stay the same through translations.

Update any automations, scripts, templates, or action calls that reference the old title-case preset values.

(@MagikalUnicorn - #172931) (Rabbit Air documentation)

Reolink

Reolink Duo PoE and Duo WiFi dual-lens cameras now expose a sub-device per lens. The camera and motion/AI sensor entities that previously had a "lens 0" or "lens 1" suffix in their name are moved to the new lens sub-devices and lose that suffix. Entity IDs and custom names stay the same, so most automations keep working.

If you target these entities through the camera device, update them to use the new lens sub-devices.

(@Markus98 - #173037) (Reolink documentation)

StarLine

The battery_level attribute has been removed from StarLine device tracker entities. Use the dedicated battery sensor in your automations and scripts instead.

(@some-random-climber - #174118) (StarLine documentation)

Tesla Fleet

The route device tracker (device_tracker.<vehicle>_route) no longer reports the active route's destination name as its state. Its state is now derived from your zones like a normal device tracker (home, not_home, or a zone name), based on the route's coordinates.

The destination name is still available through the new destination sensor (sensor.<vehicle>_destination), which is disabled by default. Enable it from the entity settings if you have automations that relied on the destination name, and update any automations that matched the old route tracker state.

(@Bre77 - #172513) (Tesla Fleet documentation)

Teslemetry

The route device tracker no longer reports the active route's destination as its state or through a location_name attribute. Its state is now derived purely from the route's coordinates (zone-aware, like home or not_home).

If you relied on the destination name, enable the new Destination sensor (sensor.*_destination), which is disabled by default and reports the destination name as Tesla provides it.

(@Bre77 - #172514) (Teslemetry documentation)

Tractive

The battery_level attribute has been removed from Tractive device tracker entities. Use the dedicated battery sensor in your automations and scripts instead.

(@bieniu - #172756) (Tractive documentation)

Zeroconf

The legacy requires_api_password field has been removed from the Home Assistant zeroconf/mDNS discovery announcement (_home-assistant._tcp). It had been hardcoded to true since the http.api_password authentication mechanism was removed in Home Assistant 2024.7, so it no longer carried any meaning. The official companion apps already ignore it.

Third-party discovery clients that still read this field need to tolerate its absence.

(@agners - #173090) (Zeroconf documentation) (API documentation)

Zone

The state (person count) and persons attribute of zone entities are now calculated from the in_zones attribute of person entities. As a result, a person can now be counted in more than one zone at the same time. For example, a person who is home with in_zones: ["home", "near_home"] now counts toward both zone.home and zone.near_home, where previously they only counted toward zone.home.

In addition, the state of position-aware device trackers is now the smallest zone the device is in, instead of the zone whose center it is closest to.

Automations, scripts, or templates that depend on zone person counts or on device tracker zone states may need to be adjusted.

(@emontnemery - #172942, #173106) (Zone documentation)

Z-Wave JS

This release requires an updated Z-Wave JS server. You need zwave-js-server 3.9.0 or newer (schema 49):

• If you use the Z-Wave JS app, update it to at least version 1.4.0.
• If you use the Z-Wave JS UI Docker container, update it to at least version 11.19.1.
• If you run your own zwave-js-server, update it to at least version 3.9.0.

(@AlCalzone - #173309) (Z-Wave JS documentation)

AirNow

The station radius option has been removed. The 2026 AirNow API no longer uses a distance parameter, so the radius had no effect on which reporting station was used. Existing entries are updated automatically, and any radius you had set is discarded. No action is needed.

(@derekcentrico - #176740) (AirNow documentation)

Gardena Bluetooth

The valve's activation_reason sensor now reports a fixed set of values instead of free-form text. If you have automations, scripts, or templates that match on the old text values, update them to match the new ones.

(@elupus - #177187)

Edifier Infrared

If you set up the Edifier Infrared integration for the R2000DB or R2730DB speakers, some buttons were mapped to the wrong infrared codes (on the R2730DB, power and mute were swapped). The mappings are now corrected and migrated automatically. If you built automations or scripts around the old, incorrect buttons, update them to match.

(@abmantis - #177472) (Edifier Infrared documentation)

Ohme

The Ohme energy sensor has been removed. It reported an estimate of the energy stored in the car's battery rather than the energy delivered by the charger, which caused confusing jumps in the energy dashboard, and the vendor's API no longer provides a useful value.

If you tracked this sensor, use an Integration - Riemann sum helper on a power sensor to estimate the energy instead.

(@dan-r - #174664) (Ohme documentation)

Paperless-ngx

Paperless-ngx now requires a newer version of your Paperless-ngx server. The minimum supported server version is raised to 2.19, which also restores compatibility with Paperless-ngx 3.0. If your Paperless-ngx server is on version 2.18 or older, update it before you update Home Assistant.

(@IngmarStein - #176889) (Paperless-ngx documentation)

Robot vacuums

The deprecated battery_level property has been removed from the vacuum entities of several integrations. If you use a robot vacuum's battery level in an automation, script, or on a dashboard, use the vacuum's battery sensor instead.

This affects the following integrations:

• LG ThinQ
• Neato
• Romy
• Shark IQ
• SwitchBot Cloud
• Template
• TP-Link
• Xiaomi Miio

(@gjohansson-ST - #175681, #175684, #175685, #175686, #175687, #175688, #175691, #175764)

ScreenLogic

The option to configure the polling interval has been removed from ScreenLogic. Home Assistant now polls the integration at a fixed interval. If you need a different update frequency, you can set your own polling interval or trigger an update with the homeassistant.update_entity action.

(@Pinball3D - #175576) (ScreenLogic documentation)

UniFi Protect

Support for UniFi Protect AI Port devices has been removed. These devices only ever exposed diagnostic sensors, all disabled by default, and are not part of the UniFi Protect public API the integration is moving to. The AI Port device and its sensors are removed automatically when you update. You can still configure the AI Port directly in UniFi Protect.

(@RaHehl - #174378) (UniFi Protect documentation)

Detection scores are no longer available. The detection binary sensors (motion, person, vehicle, animal, and the smart-audio alarm sensors) now take their state from the UniFi Protect public API, which carries no per-event score, so their event_score attribute is gone and automations that filter on it need another condition. The event id and the detected types moved to the new Motion detection, Smart detection, and Sound detection event entities.

(@RaHehl - #174948) (UniFi Protect documentation)

UniFi Protect 7.1 or newer is now required. On an older console the integration reports that the version is too old instead of setting up. Update UniFi Protect to 7.1 or newer to keep using it.

(@RaHehl - #177620) (UniFi Protect documentation)

Volvo On Call

The Volvo On Call integration has been removed. If you have a supported Volvo, set up the newer Volvo integration instead.

(@gjohansson-ST - #175677)

Flexit Nordic (BACnet)

The deprecated fireplace mode switch entity has been removed. If you have automations or scripts that use switch.<device>_fireplace_mode, use the climate.set_preset_mode action on the Flexit climate entity with preset_mode: fireplace instead.

(@magnusoverli - #179272) (Flexit Nordic (BACnet) documentation)

KNX

KNX exposes no longer send an entity's first value to the KNX bus. Previously, this depended on timing: if the entity already had a value when the expose was set up, nothing was sent, but if the value arrived later, it was sent to the bus right away.

Now, both cases behave the same way. The first value is adopted locally without sending a telegram, but stays available for read requests and periodic sending. Later value changes are still sent as before.

To send the first value right away, turn on Send on initialization for the expose in the KNX panel, or set send_on_init: true in your YAML configuration.

(@Kolbi - #178793) (KNX documentation)

LLM APIs

LLM tool names are now prefixed with the domain of the integration that offers them. For example, GetLiveContext becomes homeassistant__GetLiveContext and HassTurnOn becomes intent__HassTurnOn. If you have a custom prompt that names a tool directly, update it to use the new prefixed name.

(@balloob - #179938)

Persistent Notification

Updating a persistent notification that already exists now triggers an update_type of updated instead of added. If you have an automation that triggers on an update_type of added to catch every new or changed notification, add updated to the list of types it triggers on.

(@davidlang42 - #171067) (Persistent Notification documentation)

UniFi Protect

The smart detection switches (for example Detections: Person, Detections: Vehicle, and the audio alarm toggles) are no longer hidden while recording is disabled. They now stay available and follow the same public API as the other camera configuration switches. Their entity IDs and what happens when you toggle them are unchanged.

(@RaHehl - #174963) (UniFi Protect documentation)

UniFi Protect 7.2.105 or newer is now required. On an older version, the integration stops setting up and tells you to update. Update UniFi Protect, then reload the integration.

(@RaHehl - #179954) (UniFi Protect documentation)

Update

Installing an update, skipping an update, and clearing a skipped update now require an administrator account. These are configuration-level actions, so they are now restricted to admins, like other sensitive actions in Home Assistant.

Automations are not affected, because they run without a user context. A script runs in the context of the user who started it, so a script that installs or skips an update now fails when a non-admin user starts it. Trigger it from an automation instead, or start it as an admin.

(@balloob - #178232) (Update documentation)

Vacuum

The deprecated battery_level property has been removed from the base vacuum entity. All core vacuum integrations were already migrated in Home Assistant 2026.8. If a custom integration still sets this property, it no longer reports a battery level; add a separate battery sensor instead.

(@gjohansson-ST - #175682) (Vacuum documentation)

Z-Wave JS

The Z-Wave actions to manage lock users and credentials (set_user, delete_user, delete_all_users, set_credential, delete_credential, and delete_all_credentials) now require an administrator account.

(@balloob - #177300) (Z-Wave JS documentation)