Home Assistant Core 2022.2.0 → 2022.3.0
10 versions, 28 breaking changes in 1 version, 0 required stops
Version by version, oldest first
2022.2.1 – 2022.2.9: no action items (9 versions)
2022.3.0 2022-03-02
Quoted from www.home-assistant.io/blog/2022/03/02/release-20223/#backward-incompatible-changes
Breaking
Z-Wave / OpenZWave
This breaking change does NOT apply to users of the Z-Wave JS integration.
This is a breaking change notice regarding the older Z-Wave and OpenZWave integrations, which both have been previously deprecated.
This release of Home Assistant Core 2022.3 will be the final release that provides these integrations. Both the old zwave and ozw integrations are pending removal for Home Assistant Core 2022.4.
The ozw integration has been deprecated before as the upstream projects we depends on, for e.g., libraries and add-on containers, are no longer maintained.
As Home Assistant is moving towards support for Python 3.10, it became clear that the old zwave integration isn't compatible and thus is going to be removed for that reason.
If you are still running your Z-Wave network on either of those deprecated integrations, we highly recommend migrating to the newer Z-Wave JS integration after upgrading to this release.
The new Z-Wave JS will provide you with a modern, more feature-rich, maintained, and stable Z-Wave stack for the future.
See our documentation for a guide on Migrating from previous Z-Wave implementations.
Breaking
ASUSWRT
The previously deprecated YAML configuration of the ASUSWRT integration has been removed.
ASUSWRT 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.
(@ollo69 - #65904) (documentation)
Breaking
AVM FRITZ!Box Call Monitor
The AVM FRITZ!Box Call Monitor integration previously migrated to configuration via the UI. Therefore, configuring the AVM FRITZ!Box Call Monitor integration via YAML configuration has now been deprecated and will be removed in a future Home Assistant release.
Your existing YAML configuration has been automatically imported and can be safely removed from your YAML configuration.
(@tkdrob - #61762) (documentation)
Breaking
ebusd
A typo was fixed in the ebusd integration for monitored condition WaterPressure. It is incorrectly named "WaterPreasure" in the code.
The documentation represents the correct value.
(@nklebedev - #66355) (documentation)
Breaking
Elexa Guardian
Elexa Guardian no longer accepts the previously deprecated entity_id parameter in service calls; automations and scripts calling those services now require a device_id parameter.
(@bachya - #65484) (documentation)
Breaking
Freebox
The freebox.reboot service is now deprecated and replaced by a dedicated reboot button entity; please use that entity to reboot the Freebox instead.
(@epenet - #65501) (documentation)
Breaking
IKEA TRÅDFRI
The native IKEA Tradfri groups are now deprecated, and this feature will be removed from the integration in a future release.
Tradfri groups rely on sending frequent requests (polling) to the gateway to check the states of the groups. Continuously polling the gateway causes stability issues of the gateway, sometimes causing it to crash and requiring a restart. We propose using light groups instead.
Configuring IKEA Tradfri via YAML configuration has been deprecated and will be removed in a future Home Assistant release. Any remaining YAML configuration has been automatically imported for a long time and thus can be safely removed from your YAML configuration.
(@ggravlingen - #65226) (documentation)
Breaking
International Space Station (ISS)
The International Space Station (ISS) integration migrated to configuration via the UI. Configuring International Space Station (ISS) 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.
Breaking
MQTT
MQTT binary sensors, lights, fans, humidifiers, and switches can now have an unknown state in case the state is unknown.
This change was made to make the MQTT entities more consistent with how these entities behave in other parts of Home Assistant. You may need to adapt your script and automations to this change.
(@jbouwh - #65183 #65308 #65301 #65302 #65294) (documentation)
An MQTT configuration in configuration.yaml no longer results in an imported integration entry, MQTT must now be set up from the frontend.
Please note that:
- Any previously imported configuration is still valid, this PR does not remove or modify imported configurations.
- It's still possible to configure MQTT entities and advanced broker configurations, such as SSL certificates, via YAML.
(@emontnemery - #66160) (documentation)
The MQTT climate hold and away mode configuration settings are now deprecated and removed in Home Assistant Core 2022.9.0.
Please use the new preset_mode configuration options instead.
(@jbouwh - #66062) (documentation)
Configuring basic MQTT broker options with YAML is now deprecated, this affects the following configuration variables:
birth_messagebrokerdiscoverypasswordportusernamewill_message
Configuring those options can instead be done via the UI.
(@emontnemery - #66247) (documentation)
Breaking
Nest
Older Nest cameras no longer use thumbnail images from events, and instead always use the live stream.
You should use the newer Nest Media Source APIs to fetch media for events.
(@allenporter - #66427) (documentation)
Breaking
NINA
Districts of Hamburg and Berlin have been removed. Alternatively, Hamburg, Freie und Hansestadt and Berlin, Stadt can be used.
(@DeerMaximum - #65914) (documentation)
Breaking
Overkiz (by Somfy)
Previously, a Myfox Camera Shutter was mapped to a (non-functional) cover entity. This is now changed to be a functional switch entity instead.
(@iMicknl - #66088) (documentation)
Breaking
Phone Modem
The modem_callerid.reject_call has been deprecated and will be removed in Home Assistant 2022.4.
The integration now provides a button entity that can be used instead.
If you have been using the reject_call service in your automation or scripts, you will need to adopt those to this change.
(@tkdrob - #66742) (documentation)
Breaking
Picnic
The sensors for the "last order ETA start/end" have been renamed to "next delivery ETA start/end" and will now contain the ETA of the first upcoming delivery.
If multiple deliveries are planned, the next_delivery_* sensors contain information about the first upcoming delivery, while the last_order_* sensors contain information about the last-placed order.
(@corneyl - #66474) (documentation)
Breaking
Plugwise
Changing the scan interval option of Plugwise devices in the integration configuration has been removed. Home Assistant will, by default, use a sane and safe interval.
If you, however, still need to customize the interval, you can do so by disabling automatic updates for the integration and using an automation to trigger on your preferred interval and call homeassistant.update_entity service.
(@frenck - #65808) (documentation)
The Plugwise Auxiliary sensor entities for heating and cooling have been removed and replaced by equivalent binary_sensor entities.
(@frenck - #66259) (documentation)
Breaking
Radarr
The "Wanted" option for the Radarr integration has been removed, as this was an invalid endpoint.
If you have this option configured in your YAML configuration, you will need to remove it.
(@tkdrob - #63818) (documentation)
Breaking
Renault
Previously, Renault binary_sensor entities could have the state on or off, and in case the endpoint was unreachable: unavailable.
However, it wasn't able to have the unknown state, which has been added.
So, a binary_sensor entity can now have the on, off, unavailable, or unknown state.
You might need to adapt your automations or scripts to account this new unknown state.
(@epenet - #65997) (documentation)
Breaking
Sensibo
The optional battery voltage attribute has been removed from the climate entity. If you used this attribute in your automations or scripts, you'll need to adjust them to handle this change.
Breaking
SimpliSafe
SimpliSafe no longer accepts the, previously deprecated, system_id parameter in service calls; automations and scripts calling those services now require a device_id parameter instead.
(@bachya - #65483) (documentation)
Breaking
Sonarr
Sonarr v2 is no longer supported and has been deemed End of Life by its developers since early 2021. Please upgrade to Sonarr v3 to continue using the Sonarr integration.
The attribute date format of the Wanted sensor is now isoformated with a time of airing.
(@ctalkington - #65349) (documentation)
Breaking
Synology DSM
The Home-Mode switch of the Surveillance Station is no longer categorized to be a configuration entity since it is part of the primary functionality.
(@mib1185 - #65949) (documentation)
Breaking
Twitch
The old Twitch API, this integration previously relied on, is shutting down soon.
Therefore, this release updated the Twitch integration to support the new API, and now requires a client_secret as well as a client_id, and new OAuth tokens need to be issued with the user:read:subscriptions scope.
(@Doridian - #67153) (documentation)
Breaking
Updater
The Updater integration has been deprecated; other integrations have replaced all its functionality. It is no longer a part of default_config, and if you have the updater integration defined directly in your YAML configuration, please remove it.
- For the
binary_sensor.updaterentity, you can set up the Version integration with the "Home Assistant Website" source to get the same functionality back. - The configuration options
reportingandinclude_used_componentsfor theupdater:configuration entry was deprecated in 2021.4. If you still want to share that, please use the new Analytics integration.
(@ludeeus - #67038) (documentation)
Breaking
Vallox
The previously deprecated vallox.set_profile service has now been removed. Please use the standard fan.set_preset_mode service as a replacement.
Breaking
Viessmann ViCare
The sensor solar power production has been removed. This sensor was a collection of multiple values.
Instead, we now provide four new sensors that each provides the data as single value:
solar power production todaysolar power production this weeksolar power production this monthsolar power production this year
You might need to adapt your automations or scripts to this change. The stale restored sensor can be safely removed.
(@tschnilo - #63339) (documentation)
Breaking
Workday
Workday now requires a 2-character ISO 3166-1 country code instead of the country's name. States, provinces and constituent countries must now be listed using the province setting. Please see the documentation for examples.
Breaking
XBee
The Xbee integration has been disabled due to the third-party library we depend on not being compatible with Python 3.10.
Home Assistant is working towards adding support for Python 3.10, and we had to disable this integration now to be able to get our development and testing environments upgraded.
Breaking
Z-Wave JS
The zwave_js.ping service is now deprecated in favor of a new ping button entity. You can replace any zwave_js.ping service calls in your automation with a button.press call against the new entity with no change in functionality.
The zwave_js.ping service will be removed in a future release of Home Assistant.
(@raman325 - #66129) (documentation)
With this release, you will need to update your zwave-js-server instance.
- If you use the zwave_js add-on, you need to have at least version
0.1.54.. - If you use the Z-Wave JS 2 MQTT add-on, you need to have at least version
0.35.2. - If you use the zwavejs2mqtt Docker container, you need to have at least version
6.5.2. - 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.15.0.
(@raman325 - #66785) (documentation)
Your Z-Wave controllers will no longer get a node status sensor. While this is technically a breaking change, in practice it should not be because the controller is always alive.
(@raman325 - #67209) (documentation)
Note
Farewell to the following
The following integration is no longer available as of this release:
- Growl (GnGNTP) has been removed. The Growl project has retired. (@frenck - #65741)
From www.home-assistant.io/blog/2022/03/02/release-20223/#farewell-to-the-following
Release notes from github.com/home-assistant/core/releases, and the official release blog, checked 17 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).