Home Assistant Core 2021.9.0 → 2021.10.0
8 versions, 27 breaking changes in 1 version, 0 required stops
Version by version, oldest first
2021.9.1 – 2021.9.7: no action items (7 versions)
2021.10.0 2021-10-06
Quoted from www.home-assistant.io/blog/2021/10/06/release-202110/#backward-incompatible-changes
Breaking
Templates
The following template filters and functions will now log a warning instead of silently returning the input if the input is invalid and no default value is specified:
acosas_timestampasinatanatan2cosfloatlogmultiplyroundsinsqrtstrptimetantimestamp_customtimestamp_localtimestamp_utc
The float filter will now log a warning instead of silently returning 0 if the input is invalid and no default value is specified.
In Home Assistant Core 2021.12 the template will fail to render if no default value is specified. You can specify a default value by passing to the filter like this: {{ "abc" | float(default=0) }}.
(@emontnemery - #56453)
Breaking
Material Design Icons (MDI)
The Material Design Icons have been upgraded to v6, which brings in around 400 new icons and removes and renames some others.
The removed and renamed icons will keep working for this and the next release, Home Assistant will write a warning to the logs in case you are using one of the removed or renamed icons.
The following icons have been removed:
adobe-acrobatadobeamazon-alexaamazonandroid-autoandroid-debug-bridgebandcampbattlenetbloggerbuffercash-usd-outlinecash-usdcellphone-android(alternative:cellphone)cellphone-iphone(alternative:cellphone)concourse-cicurrency-usd-circlecurrency-usd-circle-outlinedo-not-disturb-off(alternative:minus-circle-off)do-not-disturb(alternative:minus-circle)doubanfile-pdf(alternative:file-pdf-box)file-pdf-outline(alternative:file-pdf-box)file-pdf-box-outline(alternative:file-pdf-box)google-photoshome-currency-usdlaptop-chromebook(alternative:laptop)laptop-mac(alternative:laptop)laptop-windows(alternative:laptop)microsoft-edge-legacymicrosoft-yammerpdf-box(alternative:file-pdf-box)plus-one(alternative:numeric-positive-1)poll-box(alternative:chart-box)poll-box-outline(alternative:chart-box-outline)tablet-ipad(alternative:tablet)telegramuntappdvkxamarian-outlinexingy-combinator
The following icons have been renamed:
apple-airplaytocast-variantapplicationtoapplication-outlineapplication-cogtoapplication-cog-outlineapplication-settingstoapplication-settings-outlinebolnisi-crosstocross-bolnisiboom-gate-uptoboom-gate-arrow-upboom-gate-up-outlinetoboom-gate-arrow-up-outlineboom-gate-downtoboom-gate-arrow-downboom-gate-down-outlinetoboom-gate-arrow-down-outlinebuddhismtodharmachakracellphone-erasetocellphone-removeceltic-crosstocross-celticchristianitytocrosschristianity-outlinetocross-outlinefacetoface-manface-outlinetoface-man-outlineface-profile-womantoface-woman-profileface-shimmertoface-man-shimmerface-shimmer-outlinetoface-man-shimmer-outlineflash-circletolightning-bolt-circlefloor-lamp-varianttofloor-lamp-torchiere-variantgiftofile-gif-boxgradienttogradient-verticalhandtohand-front-righthand-lefttohand-back-lefthand-righttohand-back-righthinduismtoomhuman-greetingtohuman-greeting-variantiframetoapplication-bracketsiframe-outlinetoapplication-brackets-outlineiframe-arraytoapplication-arrayiframe-array-outlinetoapplication-array-outlineiframe-bracestoapplication-bracesiframe-braces-outlinetoapplication-braces-outlineiframe-parenthesestoapplication-parenthesesiframe-parentheses-outlinetoapplication-parentheses-outlineiframe-variabletoapplication-variableiframe-variable-outlinetoapplication-variable-outlineislamtostar-crescentjudaismtostar-davidmonitor-cleantomonitor-shimmerpharmacytomortar-pestle-plussparklestoshimmerteachtohuman-male-boardtelevision-cleantotelevision-shimmertext-subjecttotext-longtwitter-retweettorepeat-variantvoice-offtoaccount-voice-off
Breaking
Alexa
Removes the support for legacy fan speeds.
Using speeds ('off', 'low', 'medium' or 'high') for the fan platform became deprecated with Home Assistant Core 2021.07, while preset modes and percentage support was added.
(@jbouwh - #55174) (alexa docs)
Breaking
AVM FRITZ!Box Tools
In order to introduce the new link status binary sensor, the previous connectivity sensor has been renamed to connection.
Please check both your Lovelace configuration and your automations to reflect this change.
(@chemelli74 - #55446) (fritz docs)
Breaking
Breaking
DLNA Digital Media Renderer
The DLNA Digital Media Renderer integration migrated to configuration via the UI. Configuring DLNA Digital Media Renderer via YAML configuration has been deprecated and will be removed in a future Home Assistant release.
Your existing YAML configuration is automatically imported on upgrade to this release; and thus can be safely removed from your YAML configuration after upgrading.
(@chishm - #55267) (dlna_dmr docs)
Breaking
HomeKit
When an iOS device wakes up it has to refresh all the A records for each paired accessory. When there are many paired accessories this can result in HomeKit timing out before it can refresh all the records and declaring some accessories unavailable.
We now use the same server name for all HomeKit bridges and accessories on a single Home Assistant instance. This allows the system to avoid doing multiple lookups since it only needs to find one A record when waking from sleep.
iOS devices and Home Hubs (Apple TVs / HomePods / iPads) may cache the server name even if it expires and may require a reboot to see the new name. If this is the case, accessories may show unavailable when outside the home until ALL home hubs are rebooted.
Breaking
Honeywell Lyric
The polling interval of the Honeywell Lyric integration has been decreased to 300 seconds to reduce chances of hitting API limit.
(@timmo001 - #56393) (lyric docs)
Breaking
Breaking
Modem Caller ID
The Modem Caller ID integration migrated to configuration via the UI. Configuring Modem Caller ID via YAML configuration has been deprecated and will be removed in a future Home Assistant release.
Your existing YAML configuration is automatically imported on upgrade to this release; and thus can be safely removed from your YAML configuration after upgrading.
(@tkdrob - #46677) (modem_callerid docs)
Breaking
Moon
The Moon entity would never have a primary moon phase state. So the state of the moon would go from Waxing gibbous directly to Waning gibbous, without being Full Moon in between.
Now the Moon entity will correctly have the primary moon phases: New Moon, First Quarter, Full Moon and Third Quarter.
If you have automations relying on the state of the moon, please review them to check if they still behave as intended.
(@stefanroelofs - #55518) (moon docs)
Breaking
NETGEAR
The NETGEAR integration migrated to configuration via the UI. Configuring NETGEAR via YAML configuration has been deprecated and will be removed in a future Home Assistant release.
Your existing YAML configuration is automatically imported on upgrade to this release; and thus can be safely removed from your YAML configuration after upgrading.
(@starkillerOG - #54479) (netgear docs)
Breaking
Breaking
OpenGarage
The OpenGarage integration has previously been migrated to configuration via the UI. Configuring OpenGarage via YAML configuration has now been deprecated and will be removed in a future Home Assistant release.
Your existing YAML configuration is automatically imported on upgrade to this release; and thus can be safely removed from your YAML configuration after upgrading.
Breaking
Pi-hole
The extra attribute domains_blocked is removed from all sensors, since it is already exposed as an own sensor.
If you relied on this attribute in your automations or script, you need to adjust those to match this change.
(@mib1185 - #56076) (pi_hole docs)
Breaking
ReCollect Waste
The previously deprecated YAML configuration of the ReCollect Waste integration has been removed.
ReCollect Waste is now configured via the UI, any existing YAML configuration has been imported in previous releases and can now be safely removed from your YAML configuration files.
Breaking
Renault
The extra state attribute last_update has been normalized to the UTC timezone.
If you have any automation or scripts that relied on this, you might need to adjust those to take this into account.
(@epenet - #54745) (renault docs)
sensor.charge_mode has been moved to select.charge_mode (note: unique_id is unchanged).
(@epenet - #55494) (renault docs)
Breaking
RFXCOM RFXtrx
The previously deprecated YAML configuration of the RFXCOM RFXtrx integration has been removed.
RFXCOM RFXtrx is now configured via the UI, any existing YAML configuration has been imported in previous releases and can now be safely removed from your YAML configuration files.
(@elupus - #54173) (rfxtrx docs)
Breaking
Speedtest.net
The previously deprecated YAML configuration of the Speedtest.net integration has been removed.
Speedtest.net is now configured via the UI, any existing YAML configuration has been imported in previous releases and can now be safely removed from your YAML configuration files.
Breaking
Sure Petcare
The Sure Petcare integration has previously been migrated to configuration via the UI. Configuring Sure Petcare via YAML configuration has now been deprecated and will be removed in a future Home Assistant release.
Your existing YAML configuration is automatically imported on upgrade to this release; and thus can be safely removed from your YAML configuration after upgrading.
Breaking
System Bridge
The following additional state attributes have been removed from the existing sensors:
availablefilesystemload_averageload_idleload_systemload_usermountsizetypeused
You should update any automations and scripts that depend on these state attribute to use the separate sensors available for these states.
Breaking
TP-Link Kasa Smart
The TP-Link Kasa Smart integration migrated to configuration via the UI. Configuring TP-Link Kasa Smart via YAML configuration has been deprecated and will be removed in a future Home Assistant release.
Your existing YAML configuration is automatically imported on upgrade to this release; and thus can be safely removed from your YAML configuration after upgrading.
(@rytilahti - #56701) (tplink docs)
Breaking
Tuya
The previous Tuya API is no longer maintained by Tuya officially and the new integration will be officially maintained by the Tuya Developer Team.
If you used the integration before this release, you'd need to set it up again from scratch. To do that, remove any existing instances from the integration dashboard. After that, use our documentation for guidance on setting up the new integration.
The cover platform is not ready for this release but will be included later. If you have cover devices, they will not available for control at the moment.
(@zlinoliver - #56820) (tuya docs)
Breaking
UPnP/IGD
UPnP/IGD integration no longer supports the local_ip configuration option. If you still have this configured in your YAML configuration, please remove it.
(@StevenLooman - #55540) (upnp docs)
Breaking
Velbus
The Velbus integration migrated to configuration via the UI. Configuring Velbus via YAML configuration has been deprecated and will be removed in a future Home Assistant release.
The Velbus services calls will now need an interface parameter, this is to allow support for multiple Velbus connections. If you are using Velbus services in your automations or scripts, you may been to adjust those to this change.
(@Cereal2nd - #54032) (velbus docs)
Breaking
Xiaomi Miio
The model and mode attributes have been removed. The preset_mode attribute is available in place of the mode attribute.
The device model is available in the Device info window.
(@bieniu - #55846) (xiaomi_miio docs)
Breaking
Note
Farewell to the following
The following integrations are no longer available as of this release:
- Trackr has been removed. The API is no longer available and has therefore been removed. (@FuzzyMistborn - #55917)
- Tesla has been removed due to increased Tesla login security preventing third-parties to log in. (@alandtse - #55988)
From www.home-assistant.io/blog/2021/10/06/release-202110/#farewell-to-the-following
Release notes from github.com/home-assistant/core/releases, and the official release blog, checked 18 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).