Home Assistant Core 2024.9.0 → 2024.10.0

Climate

We have added more validation to the climate.set_humidity action, which enforces that the set target humidity is within the targeted entity's minimum and maximum humidity levels.

You should adjust automations and scripts to use valid values if you are using this action.

(@gjohansson-ST - #125242) (documentation)

ecobee

The previously deprecated aux_heat attribute has been removed from the provided climate entity.

(@gjohansson-ST - #125246) (documentation)

Honeywell Total Connect Comfort (US)

The previously deprecated aux_heat attribute has been removed from the provided climate entity.

(@gjohansson-ST - #125248) (documentation)

Humidifier

We have added more validation to the humidifier.set_humidity action, which enforces that the target humidity is within the targeted entity's minimum and maximum humidity levels.

You might need to adjust automations and scripts to use valid values if you are using this action.

(@gjohansson-ST - #125863) (documentation)

Nuki

The previously deprecated nuki_id and battery_critical attributes have been removed from the Nuki entities. If you are using these attributes in automations or scripts, you need to update those.

(@steffenrapp - #125348) (documentation)

OpenTherm Gateway

To modernize the OpenTherm Gateway integration, all entities have been split into different devices. As a result, the OpenTherm Gateway climate entity has been moved to a new OpenTherm Thermostat device.

Configurations that look for the climate entity by device must be adjusted accordingly.

In the process, all entities were reviewed and some were found to be irrelevant or superfluous. These entities have been removed. All removed entities were previously disabled by default, so anyone who has never manually enabled an entity in the OpenTherm Gateway integration is not affected by this.

All other users should review their configuration for using OpenTherm Gateway entities that no longer exist or have been assigned to another device.

(@mvn23 - #124869) (documentation)

Pentair ScreenLogic

Support for use of an area, device, or entity as a target for ScreenLogic actions has been removed. Instead, use config_entry with the entry_id of the desired ScreenLogic

Support for using an area, device, or entity as a target for ScreenLogic actions has been removed. Instead, use config_entry with the entry_id of the desired ScreenLogic.

(@dieselrabbit - #123432) (documentation)

Ping

The binary sensor attributes this integration provided have been replaced with sensor entities in Home Assistant 2024.4. These deprecated attributes have now been removed.

(@jpbede - #125760) (documentation)

Ring

The ring.update action was deprecated in the 2024.4 release and has now been removed. Please use homeassistant.update_entity if you need a replacement.

(@jpbede - #125762) (documentation)

Squeezebox (Lyrion Music Server)

We previously noticed that the squeezebox platform had deprecated the squeezebox_sync and squeezebox_unsync actions and the sync_group entity attribute in favor of the newer "join" framework common to all media players.

These deprecated actions and entity attributes have now been removed.

(@rajlaud - #125271) (documentation)

Templates

Limit maximum template render output to 256KiB to ensure template renders do not inject unreasonable data into the system and cause a crash.

256KiB is likely to still block Home Assistant’s event loop for an unreasonable amount of time, but it's likely someone is using the template engine for large blocks of data, so we want a limit that still allows that but has a reasonable safety margin to prevent the system from crashing down.

(@bdraco - #124946)

ThermoWorks Smoke

The ThermoWorks Smoke integration is disabled because it creates an unresolvable dependency conflict.

Contributions to fixing this conflict are greatly appreciated.

(@edenhaus - #125661) (documentation)

Tfiac

The Tfiac integration is disabled because we cannot create valid Python wheels for its dependencies.

Contributions to fixing this issue are greatly appreciated.

(@edenhaus - #125692) (documentation)

Z-Wave

With this release, you will need to update your zwave-js-server instance. You must use zwave-js-server 1.37.0 or greater (schema 37).

• If you use the Z-Wave JS add-on, you need at least version 0.7.0.
• If you use the Z-Wave JS UI add-on, you need at least version 3.9.0.
• If you use the Z-Wave JS UI Docker container, you need at least version 9.16.0.
• 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.37.0.

(@MartinHjelmare - #125666) (documentation)