Home Assistant Core 2024.2.0 → 2024.3.0

AEMET

The daily data for the current day wasn't available after midday, and now it will be. Automations and scripts relying on day[0] for checking the next-day forecast will have to be adjusted to use day[1] instead.

(@Noltari - #107795) (documentation)

JuiceNet

The JuiceNet integration has been removed.

Enel X has migrated from JuiceNet to JuicePass, rendering the JuiceNet integration useless. Background and alternative solutions to the juicenet integration can be found in the related issue.

(@emontnemery - #111477)

Met.no

The met.no integration previously created two entities for each configured location: one provided daily weather forecasts, and one provided hourly forecasts.

The met.no integration now only creates a single entity that provides both daily and hourly weather forecasts.

(@emontnemery - #97023) (documentation)

MQTT

Aux heat, deprecated in Home Assistant Core 2023.9, is now removed from the MQTT climate.

(@jbouwh - #109513) (documentation)

Z-Wave

For Z-Wave climate entities, the behavior of the climate.turn_on service has changed. Previously, the service would act in the following order depending on whether the corresponding conditions were met:

1. If the entity supported the off mode and exactly one additional mode, climate.turn_on would set the mode to the additional mode.
2. If conditions for 1 were not met and at least one of the following modes were available, the service would set the mode to the first mode it found in the specified order: heat_cool, heat, cool.
3. If conditions for 1 and 2 were not met, the service would silently do nothing.

Now, the service follows the following behavior in order:

1. If the entity supports the resume thermostat mode, it will be used to restore the last mode you used before the entity was turned off.
2. If the condition for 1 isn't met and the entity was turned off in Home Assistant, and Home Assistant wasn't restarted, Home Assistant remembers the last "on" mode and will set it to that mode. Home Assistant will be unable to set the entity to the previous mode if Home Assistant starts with the entity already in off mode since the integration will not know what the previous mode was.
3. If conditions for 1 and 2 are not met and at least one of the following modes is available, the service sets the mode to the first mode it finds in the specified order: heat_cool, heat, cool (no change to condition 2 above).
4. If conditions for 1, 2, and 3 are not met, the mode will be set to the first supported mode it finds (like dry or fan_only).

(@raman325 - #109187) (documentation)