Home Assistant Core 2024.11.0 → 2024.12.0

Brother Printer

The unit of measurement for pages changed from p to pages.

This could potentially break use cases if it was used in templates where a state with a unit is used, such as states('sensor.pages', with_unit=True).

(@bieniu - #131275) (documentation)

Ecovacs

Ecovacs devices not recognized by the library will no longer use the fallback vacuum. Instead, the device will not be added to Home Assistant, and a warning log will created.

(@edenhaus - #131525) (documentation)

Glances

The previously deprecated Glances v2 API has been removed. Upgrade to v3 or higher to continue using the integration.

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

History Stats

After this change, history_stats in time or ratio mode will only count definitively known time-based recorded data.

Prior to this change, if the start of the time window was earlier than the oldest datapoint in the recorder, history_stats would count time using the assumption that an entity was in the first state it found since the beginning of time. This could lead to wild overcalculations when a switch was turned on after a long period of inactivity, and history_stats would assume it had always been on and calculate a huge value based on that.

(@karwosts - #126271) (documentation)

Jewish Calendar

To support Rosh Chodesh this creates a breaking change as the holiday sensor will return "Chanukah, Rosh Chodesh" when both of those days fall on the same date. If you have an automation expecting the "Chanukah" value, you must update it.

(@tsvi - #130456) (documentation)

Plugwise

For the Plugwise Adam, all device-based climate entities will be replaced by new zone-based climate entities, which will most likely have different entity names. This change aligns with the Plugwise App's representation of climate entities as zones (as discovered in Issue #130597).

(@bouwew - #131659) (documentation)

QNAP

The QNAP sensors will no longer have the following extra state attributes:

• memory_free
• memory_percent_used
• memory_size
• memory_used
• network_err
• network_link_status
• network_max_speed
• network_rx
• network_tx
• status
• system_temp
• uptime
• volume_percentage_used
• volume_size_free
• volume_size_total
• volume_size_used

These extra state attributes were deprecated in Home Assistant 2024.6 and have now been removed. If you are using this in your automation or script, use the separate available sensors instead.

(@jbouwh - #130310) (documentation)

Spotify

The Spotify audio feature sensors have been removed since Spotify removed access for them, starting 27 November.

Additionally, featured and category playlists have been removed from the Spotify media browser since Spotify deprecated the API, starting on 27 November.

(@joostlek - #131754 #131758) (documentation)

Statistics

Previously the attributes of the entity states of the Statistics integration were only provided when they had a non None value. This has now changed so the attributes are always provided even with None values. You might need to modify your automations or scripts depending on whether these attributes are present or not.

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

Stookwijzer

The Stookwijzer sensor has migrated to the new API provided by Atlas Leefomgeving. As a result, the reported states are slightly different.

Old versus new:

• Blue (blauw) -> Yellow (code_yellow)
• Orange (oranje) -> Orange (code_orange)
• Red (rood) -> Red (code_red)

If you use the Stookwijzer sensor in your automations or scripts, you might need to adjust those for this change.

(@frenck - #131567) (documentation)

Templates

The this template variable which is available in some templatable helpers was previously based on the new state instead of the current state.

The change affects the following integrations, if templates use the this variable. The user might have to update their templates to reflect the above change using the value variable instead, which holds the new value.

• command_line
• rest
• scrape
• snmp
• sql

(@gjohansson-ST - #130135)

Z-Wave

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

• If you use the Z-Wave JS add-on, you need at least version 0.9.0.
• If you use the Z-Wave JS UI add-on, you need at least version 3.17.0.
• If you use the Z-Wave JS UI Docker container, you need at least version 9.26.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.39.0.

(@MindFreeze - #129482) (documentation)