2022.3: Select and play media

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.

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)

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)

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)

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)

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)

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)

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.

(@DurgNomis-drol – #64987) (documentation)

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_message
• broker
• discovery
• password
• port
• username
• will_message

Configuring those options can instead be done via the UI.

(@emontnemery – #66247) (documentation)

Districts of Hamburg and Berlin have been removed.
Alternatively, Hamburg, Freie und Hansestadt and Berlin, Stadt can be used.

(@DeerMaximum – #65914) (documentation)

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)

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)

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)

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)

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)

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)

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.

(@gjohansson-ST – #64753) (documentation)

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)

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)

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)

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)

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.updater entity, you can set up the
  Version integration with the
  “Home Assistant Website” source to get the same functionality back.
• The configuration options reporting and include_used_components for
  the updater: configuration entry was deprecated in 2021.4.
  If you still want to share that,
  please use the new Analytics integration.

(@ludeeus – #67038) (documentation)

The previously deprecated vallox.set_profile service has now been removed.
Please use the standard fan.set_preset_mode service as a replacement.

(@andre-richter – #66655) (documentation)

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 today
• solar power production this week
• solar power production this month
• solar 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)

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.

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.

(@frenck – #59729)

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)

In November 2020, with the release of Python pip 20.3, a new dependency
resolver was introduced in pip, which is more strict.

Home Assistant held back supporting the new pip version because of the
large number of dependencies we have, it took time for us to adjust to this
change. Meanwhile, Python pip would only warn for conflicts.

As we have resolved almost all dependency conflicts, we have now lifted
the pip version pinning, and thus now use the newer and stricter pip version.

If you use external dependencies in your custom integration, you might be
impacted by the new pip resolver. Your dependencies (and their version ranges)
must be compatible with the dependencies Home Assistant has; otherwise,
the installation of your custom integration will not succeed.

You can find more information on the new dependency resolver in Python pip here:

https://pip.pypa.io/en/latest/user_guide/#changes-to-the-pip-dependency-resolver-in-20-3-2020

We now use version 3.8+ of aiohttp, which requires async_timeout 4.0+
which has multiple breaking changes:

• async_timeout.timeout drops the loop= keyword arg.
• async_timeout.current_task has been removed.
• The timeout.remaining property has been removed.
• The timeout.timeout property has been removed.

Previously we had a backward-compatible layer in Home Assistant to
ease this change, which has now been removed.

(@frenck – #65732)

If a user has the http integration configured to use SSL,
it only accepts HTTPS traffic. This means that the internal URL needs
to be set to use HTTPS too, and for the certificate to be valid,
this needs to be a domain name.

A lot of integrations that we send the URL to will fail if the
certificate is not valid (ie. Sonos, Cast).

To help the user get this right, the default for the get_url helper
will now prefer the external address if SSL is configured.

This has a higher chance of being correct, delivering a better out-of-the-box
experience to a larger group of users.

(@balloob – #66039)

split_entity_id will now raise a ValueError if the passed value
does not follow the basic entity ID format
(<domain>.<object id>).

Previously it could return a list with a single item.

(@balloob – #66835)

When using datetime and date device classes in sensors, the returned
native value must (respectively) be a datetime or date Python object.

Returning an iso formatted date(time) string in these cases was
previously deprecated and the fallback/backward compatibility has now
been removed.

(@frenck – #65734)

Currently, zeroconf returns IPv4 addresses in the host field. If there were
no advertised IPv4 addresses, the discovery would fail. For example,
a specific manufacturer’s Thread Border Router advertised devices as
IPv6-only zeroconf services.

IPv6-only devices can now be discovered and an IPv6 address will
be present in the host property for those devices.

Developers who need to filter discovered devices by IP address version
should use homeassistant.util.network.is_ipv4_address or
homeassistant.util.network.is_ipv6_address to reject zeroconf
discoveries they do not want.

(@roysjosh – #66455)