Home Assistant Core 2021.4.0 → 2026.9.4

Container udev

We no longer run an udev instance inside our containers. This was used by the Supervisor which now is using the host udev in all containers.

For now, we have a fallback environment variable USING_UDEV=1 which you can set on your container to get the old behavior. This gives you time for using the Docker way to map/use devices.

If you run a system that uses the Supervisor, this is automatically taken care of.

(@pvizeli- #180)

Custom integrations

Custom integrations now require a version key in their manifest file, this also means that all custom integrations now require a manifest file.

If you are using a legacy custom integration like custom_components/awesome.py this now needs to move to custom_components/awesome/__init__.py so you can add custom_components/awesome/manifest.json to it.

For more information about integration, manifests have a look here: https://developers.home-assistant.io/docs/creating_integration_manifest

Custom integrations that do not have this will be blocked from loading if it’s missing a version in the manifest starting with Home Assistant 2021.6.

If you see these errors, please report the issue with the author of that custom integration.

(@ludeeus - #49726)

Events

An event fired with an event_type of more than 64 characters would previously result in recorder errors but the event would otherwise work. Now, firing an event with more than 64 characters in the event type will raise immediately.

If you are using long events in your automations or scripts, you should adjust to this change. Custom integration authors should review their event types.

(@raman325 - #48115)

ASUSWRT

The device_tracker entity state attribute ip_address has been changed and is now be named ip. You need to update automations and scripts that use this attribute.

(@bieniu - #48764)

AVM FRITZ!Box Tools

The AVM FRITZ!Box Tools integration is now configured via the UI. Configuring the integration via YAML is now deprecated. Existing YAML configuration is automatically imported on upgrade and can be safely removed after upgrade.

(@chemelli74 - #48287)

AVM FRITZ!SmartHome

YAML configuration for AVM FRITZ!SmartHome has been removed, after it has been deprecated for 12 months. Configuration via UI is fully integrated. Existing YAML configuration has already been imported automatically in the previous releases and can now safely be removed from your configuration files.

(@mib1185 - #49663)

DHT Sensor

The pin configuration option is currently an integer but will need to be prefixed with D for Raspberry Pi platforms.

Please adjust your YAML configuration for this change.

(@TheGardenMonkey - #41525)

ecobee

ecobee climate devices will change the reported temperature precision for their current_temperature attribute from whole degrees to 0.1 degree increments. Automations which rely on whole-number precision may need adjustments.

(@jjlawren - #48697)

Setting a fan hold in the ecobee integration will no longer also set a temperature hold. If any automations assumed that the temperature would be set when calling the set_fan_mode service on an ecobee device, those automations will need to add the appropriate set_temperature service call.

(@bjpetit - #48086)

Enphase Envoy

Enphase Envoy has fully transitioned to configuration via UI. YAML configuration will be removed in an upcoming version. Existing YAML configuration will be imported automatically, and can now safely be removed from your configuration files.

All sensors are now configured by default. Each inverter has a unique ID and can now be disabled in the UI.

(@bdraco - #48517)

Ezviz

The Ezviz integration is now configured via the UI. Configuring the integration via YAML is now deprecated. Existing YAML configuration is automatically imported on upgrade and can be safely removed after upgrade.

All camera state attributes were removed and replaced by binary_sensors, sensors or switches.

List of old camera state attributes with their new replacements:

• "privacy": switch entity, camera_name.privacy
• "audio": switch entity, camera_name.sound
• "ir_led": switch entity, camera_name.infrared
• "state_led": switch entity, camera_name.light
• "follow_move": switch entity, camera_name.tracking
• "alarm_notify": camara status, "Recording"
• "alarm_sound_mod": sensor, camera_name.alarm_sound_mod
• "encrypted": binary_sensor, camera_name.encrypted
• "local_ip": sensor, camera_name.local_ip
• "detection_sensibility": sensor, camera_name.detection_sensibility

If you are using one of these attributes in your automations or scripts, you will need to adjust to this change.

(@RenierM26 - #45722)

Garmin Connect

The unit of measurement from Garmin Connect timestamp sensors has been removed. It used to be set to empty string. If you have automations, scripts or external data recvorder that rely on unit of measurement for these sensors, you might need to adjust to this change.

(@MartinHjelmare - #48431)

GNTP (Growl)

The GNTP (Growl) integration has been deprecated and is going to be removed in Home Assistant Core 2021.6.

The Growl project has now fully retired, see: https://growl.github.io/growl/

(@frenck - #49273)

Google Travel Time

The Google Travel Time integration is now configured via the UI. Configuring the integration via YAML is now deprecated. Existing YAML configuration is automatically imported on upgrade and can be safely removed after upgrade.

(@raman325 - #43509)

Hive

The existing Hive service heating_boost will be deprecated in Home Assistant release 2021.6 and a new service to replace it has been created called heating_boost_on.

If you use the heating_boost Hive service please update your configuration to the new service. A deprecation warning will be printed to the logs when the deprecated service is used.

(@KJonline - #48701)

KNX

The config_file YAML option for KNX was deprecated before and has now been removed.

(@marvin-w - #48799)

Light profiles

When a light entity has a default profile associated, the default profile will only be applied for the light.turn_on service call when the light state is off or no data is sent with the service call.

The transition attribute from the default profile in light_profiles.csv will also be applied when light.turn_off is called.

(@karliemeads - #49376) (light docs)

Litter-Robot

reset_waste_drawer, set_sleep_mode, and set_wait_time now have their own services. Previously, they were triggered by using send_command. If you used any of those commands in your automations or scripts, you'll need to replace them with their service counter-part.

(@natekspencer - #48300)

Modbus

A new option SWAP replaces REVERSE_ORDER, however REVERSE_ORDER is still accepted and silently converted to SWAP=WORD.

Note: REVERSE_ORDER will be removed in a future release.

Old configuration example:

modbus:
  sensors:
    - name: "sensor1"
      address: 17
      reverse_order: true
      ...
   - name: "sensor2"
      address: 17
      reverse_order: false
      ...

New configuration example:

modbus:
  sensors:
    - name: "sensor1"
      address: 17
      swap: word
      ...
   - name: "sensor2"
      address: 17
      swap: none
      ...

Swap allows none/byte/word/word_byte options.

(@janiversen - #49719)

Recollect Waste

Recollect Waste pickup dates are now stored as UTC timestamps.

(@bachya - #48690)

Recorder

Database migrations are now done in the background and no longer prevent Home Assistant from starting.

The migration is started shortly after the started event since they are CPU intensive (mostly just sqlite since it's in the same process) and we do not want to compete with startup.

Events created by your system are queued and processed when the migration is completed. There is a safety to start discarding events if more than ~30000 events happen before migration is completed to avoid memory exhaustion.

During migration, Home Assistant will prevent being started or stopped and this will also disable the homeassistant.stop and homeassistant.start services until the migration has been completed.

The sqlite database recovery logic can now recover at point after setup including purge, migration, and event insert. In short we can always (hopefully) recover and start a new db without a restart.

The quick check is no longer performed on unclean shutdown since we can always recover live. The db_integrity_check option has been deprecated.

(@bdraco - #49036 #49098)

If you are using a PostgreSQL database please verify that your connection URL starts with postgresql://. In case you use still an old URL starting with postgres://, please replace it with postgresql:// otherwise you will get an error to set up the recorder.

RoonLabs music player

The RoonLabs music player media_player previously had integration specific services for roon.join and roon.un_join. These have been removed removes and replaced with the media_player.join and media_player.unjoin services.

If you use these services in your automations or script, you need to adjust those.

(@pavoni - #49667)

Shelly

The Shelly Wi-Fi RSSI sensor unit was wrong, it is dBm and not dB. If you rely on the unit of measurement from this sensor, you might need to adjust to this change.

(@thecode - #49265)

SimpliSafe

The unpublished SimpliSafe cloud API no longer provides a functioning websocket. Therefore, the integration will no longer be able to receive SIMPLISAFE_EVENT or SIMPLISAFE_NOTIFICATION events, nor will it be possible for stage changes performed outside of Home Assistant (e.g., via the keypad) to be reflected in Home Assistant in near-realtime.

(@bachya - #49876) (simplisafe docs)

SMA Solar

The SMA integration is now configured via the UI. Configuring the integration via YAML is now deprecated. Existing YAML configuration is automatically imported on upgrade and can be safely removed after upgrade.

Using custom sensors is deprecated and not possible using the UI. Feel free to submit additional sensors to be added as standard sensors to the pysma library.

The pv_power sensor is now reporting DC power of solar panels side A and named pv_power_a for new installations. grid_power is the total power supplied to the grid.

(@rklomp - #48003)

Sure Petcare

The following YAML configuration options have been deprecated:

• feeders
• flaps
• pets
• scan_interval

If you have one of these options in your YAML configuration, you can safely remove those.

(@benleb - #49223)

Swiss Hydrological Data

FEON/BAFU changed their data which required removing some of the attributes.

The following attributes are no longer available:

• delta-24h
• max-1h
• min-1h
• mean-1h
• previous-24h

(@Bouni - #49119)

System Monitor

The unit of measurement from System Monitor timestamp sensors has been removed. It used to be set to empty string. If you have automations, scripts or external data recorder that rely on unit of measurement for these sensors, you might need to adjust to this change.

(@MartinHjelmare - #48431)

Tasmota

Tasmota lights no longer supports deprecated white_value, use rgbw_color instead.

(@emontnemery - #49599) (tasmota docs)

The Tasmota Wi-Fi RSSI sensor unit was wrong, it is dBm and not dB. If you rely on the unit of measurement from this sensor, you might need to adjust to this change.

(@thecode - #49263) (tasmota docs)

Waze Travel Time

The Waze Travel Time integration is now configured via the UI. Configuring the integration via YAML is now deprecated. Existing YAML configuration is automatically imported on upgrade and can be safely removed after upgrade.

(@raman325 - #43419)

ZeroConf

If the default_interface is not set, the value is auto-detected based on the system routing next hop for the mDNS broadcast address (224.0.0.251).

If the next-hop cannot be detected or is a loopback address, zeroconf will broadcast on all interfaces. If the next hop is a non-loopback address, zeroconf will only broadcast on the default interface.

Setting the default_interface to true or false will override the auto detection.

(@bdraco - #49529)

Farewell to the following

The following integrations are no longer available as of this release:

• Geizhals has been removed. (@frenck - #48594)
• Social Blade has been removed. (@frenck - #48677)

Both integrations were in a broken state and using webscaping methods to gather their data, which is not allowed for core integrations.

HTTP (using reverse proxies)

Home Assistant will now warn when a misconfigured reverse proxy, or misconfigured Home Assistant instance when using a reverse proxy, has been detected.

These warnings will become an error in Home Assistant 2021.7.

If you are using a reverse proxy, and see these warnings, please make sure you have configured use_x_forwarded_for and trusted_proxies in your HTTP integration configuration.

For more information, see the HTTP integration documentation.

(@frenck - #51332)

Custom cards

We upgraded our frontend to use Lit 2.0. During the beta we have noticed some custom cards or views are using LitElement and lit-html from our components.

This is not a recommended practice, and might now cause the custom card to break this release. If you encounter issues with a custom card, please report this issue with the custom card developer.

Additional information about this change and information for custom card developers on how to upgrade their card, can be found in our developer blog:

"Upgrade to Lit 2.0"

Custom integrations (custom_components)

As mentioned in every release since 2021.3, custom integrations will require a version key in their manifest file.

As of this release, if that version key is missing in the manifest, the custom integration will no longer be loaded.

For more details see our developer blog about it

(@ludeeus - #49916)

1-Wire

Support for OWFS has been dropped (obsolete since 0.117).

This part of the implementation did not conform to policy regarding 3rd-party libraries of Home Assistant.

(@epenet - #50121) (onewire docs)

Denon AVR

Alexa EqualizerController has been disabled for Denon AVR since it caused Alexa to be unable to discover any devices.

(@starkillerOG - #49628) (Alexa docs)

AVM FRITZ!Box Tools

Since in most cases, the amount of really wanted to be tracked devices is quite lower than the overall count of devices, device_tracker entities will be disabled by default. You need to specifically enable wanted device_tracker, even newly detected devices.

(@mib1185 - #50791) (fritz docs)

Blebox

Blebox light no longer supports the deprecated white_value, use rgbw_color instead.

(@emontnemery - #49562) (blebox docs)

Buienradar

Buienradar is now configurable via the UI and has deprecated support for the YAML configuration. Your existing YAML configuration will be imported once.

When you have a weather and sensor setup for same coordinates, they will be merged into one integration instance. Only one camera configuration will be imported.

Following things are changed:

• The forecast key of the weather platform is deprecated, forecast data is fetched in the same API call and to be in line with ADR-0003, all available data is exposed.
• Weather, sensor and camera domain are setup in one integration. For new entries, sensor and camera entities are disabled by default.
• Dimension for camera images is fixed to 700 pixels.

(@RobBie1221 - #37796) (buienradar docs)

EE Bright Box

The integration library requirement has requirements that are conflicting with requirements of other integrations. The library maintainer hasn't responded to our issues for 10 months.

The integration is therefore disabled until the library has been fixed and Home Assistant updated with a new library version.

(@MartinHjelmare - #51069) (ee_brightbox docs)

Epson

Epson integration doesn't allow port set anymore. It uses port 80 and 3629 for communication.

(@pszafer - #45434) (epson docs)

Goal Zero Yeti

The 12V, AC, and USB binary sensors are now switches. You should update any automations and scripts that depend on these moved entities.

Before: binary_sensor.yeti_ac_port_status After: switch.yeti_ac_port_status

(@tkdrob - #48612) (goalzero docs)

HomeKit Controller

HomeKit Controller climate devices will change the reported temperature precision for their current_temperature attribute from whole degrees to 0.1 degree increments when the system is in Fahrenheit mode.

Automations which assume whole-number reporting precision may need adjustments.

(@jjlawren - #50415) (homekit_controller docs)

KNX

The create_temperature_sensors option for climate devices is now deprecated. Please use a template sensor instead.

This option created sensor entities out of climate configuration. This will not work anymore when sensor entities are also only generated from configuration.

(@farmio - #49638) (KNX docs)

---

The create_sensors option for weather entities is now deprecated. Please use template sensors instead.

This option created sensor entities out of weather configuration. This will not work anymore when sensor entities are also only generated from configuration.

(@farmio - #49640) (KNX docs)

Luftdaten

The unit of measurement for the Luftdaten pressure sensors has been adjusted from pascal (Pa) to hectopascal (hPa). The value is still the same, the unit displayed in Home Assistant was wrong and now corrected.

If you have automation or record data from this integration (externally), you might need to adjust to this change.

Modbus

The old configuration style for switches is no longer supported

# old configuration.yaml:
modbus:
    - name: "mymodbus"
      ....

switches:
    - name: "switch12"
       hub: "mymodbus"

# new configuration.yaml:
modbus:
    - name: "mymodbus"
       ....
       switches:
         - name: "switch1"

The new configuration style have changed, to secure against illegal configurations:

# before configuration.yaml:
modbus:
    - name: "mymodbus"
      ....
      switches:
          - name: "switch1"
             input_type: "holding"
             verify_state: false

# new configuration.yaml without verify:
modbus:
    - name "mymodbus"
       ....
       switches:
          - name switch1
             write_type: "holding"

# new configuration.yaml with verify:
modbus:
    - name: "mymodbus"
       ....
      switches:
        - name: "switch1"
           write_type: "holding"
           verify:

(@janiversen - #49386) (modbus docs)

---

scan_interval, if used, in any Modbus platform cannot be lower than 5 seconds. Adjustment is done automatically with a warning if needed.

Modbus timeout, if used, is automatically adjusted (with a warning) to not be higher than lowest scan interval - 1 second.

(@janiversen - #50363) (modbus docs)

MQTT

Peviously deprecated features of MQTT cover have been removed:

• Using value_template to use for extracting position is no longer allowed an error will be raised if this configuration is used, Instead of using value_template, position_template should be used.
• tilt_invert_state is removed, instead tilt_min and tilt_max should be used, error will be raised if this is found in configuration.

(@thecode - #50263) (MQTT docs)

---

If you use MQTT with the CloudMQTT broker service and have not configured a certificate for MQTT, you now need to adjust to the following:

mqtt:
  certificate: auto
  host: ... # all other info

(@balloob - #51112) (MQTT docs)

Network / Zeroconf

Network adapter configuration has moved to the UI. Users that previously used a custom zeroconf interface configuration may need to adjust the settings in the UI.

(@bdraco - #50874) (network docs)

Sonos

The device associated with Sonos speakers will report a different firmware version, switching to the more common formatted version number from now on.

(@jjlawren - #50861) (Sonos docs)

TensorFlow

Support for the TensorFlow integration is now deprecated on the Home Assistant OS, Supervised & Container installation types.

Support for it will be removed in Home Assistant 2021.7.

The use of the TensorFlow integration on the Home Assistant Core installation type, will remain available.

Tibber

Attributes for the Tibber Pulse sensor are removed and replaced by separate sensors.

Additionally the unique ID are changed, which might have caused changes to the entity IDs.

You need to to check you entities and automations and adjust them to these changes.

(@Danielhiversen - #50418) (tibber docs)

TP-Link Kasa Smart

This changes the behavior of turning a bulb when no parameters are defined. Turning on a bulb without additional parameters will now result in a "Last On" state rather than any sort of preset that may have been set in Kasa.

(@gabrialdestruir - #50334) (tplink docs)

Utility Meter

The last_reset state attribute of utility_meter sensors are now in UTC and stored as a string.

Automations and scripts accessing the last_reset state attribute may need to be updated.

(@emontnemery - #51067 #50851) (utility_meter docs)

Z-Wave JS

Z-Wave JS lights no longer support the deprecated white_value, use rgbw_color instead.

(@emontnemery - #49588) (zwave_js docs)

---

Users should update zwave-js-server to 1.7.0 or higher. If the official Home Assistant Z-Wave JS add-on is used, add-on version 0.1.23 and higher will include zwave-js-server 1.7.0.

(@MartinHjelmare - #51341) (zwave_js docs)

Farewell to the following

The following integrations are no longer available as of this release:

• LIFX Legacy has been removed, use the LIFX integration instead. (@frenck - #50069)
• N26 has been removed due to 3rd party API limitations. (@zhulik - #50292)
• Spot Crime access to their API cannot be gained anymore. (@frenck - #50361)

Using a reverse proxy with Home Assistant

Home Assistant will now block HTTP requests when a misconfigured reverse proxy, or misconfigured Home Assistant instance when using a reverse proxy, has been detected.

If you are using a reverse proxy, please make sure you have configured use_x_forwarded_for and trusted_proxies in your HTTP integration configuration.

For more information, see the HTTP integration documentation.

Additionally, access to Home Assistant from the same IP address as a trusted proxy will be rejected if the request is marked as forwarded.

(@frenck - #51839) (http docs)

Python 3.9 / Alpine 3.13

Our Docker images are now based on Alpine 3.13 and run Python 3.9.

This is mainly interesting if you running custom Docker containers based on our container.

If you are using Home Assistant Container, Home Assistant OS or the Home Assistant Supervised installation method, you will automatically get this update on upgrade and no additional interaction is needed.

Please note, that Alpine 3.13 on ARM devices running a 32-bits operating system (armhf/armv7), requires your Docker version to be at least 19.03.9 (although, we recommend updating to an even higher version). Additionally, you need to have libseccomp 2.42 or newer.

(@pvizeli - #51628)

Airly

The AirQuality platform has been marked as deprecated. The air_quality entity is removed and replaced with sensor entities. You will need to update their automations and dashboards if you have been using the air_quality entity of Airly.

(@bieniu - #52225) (airly docs)

Azure Event Hub

When using this integration with IoTHub, the event_hub_name is now a required field can be filled by the DeviceID when using IoTHub.

(@eavanvalkenburg - #52049) (azure_event_hub docs)

CEC Support

Our Docker container has limited support for CEC drivers to those provided by the Linux kernel. This applies to the Home Assistant Container, Home Assistant OS and Home Assistant Supervised installation types.

This will cover most CEC drivers out there.

(@pvizeli - #51637)

Coinbase

The Coinbase integration migrated to configuration via the UI. Configuring Coinbase 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.

(@TomBrien - #45354) (coinbase docs)

---

Only accounts explicitly included in account_balance_currencies will be loaded. Excluding the option will no longer load all provided accounts as Coinbase's API now provides at least 29 accounts even if they are not configured in your API settings on Coinbase.

(@TomBrien - #51981) (coinbase docs)

Database (statistics table)

The statistics table is a Home Assistant data table that is not exposed or used by Home Assistant yet and is part of an alpha / feature that is in development. However, it does exist and you might already want to check it out or find a use for it.

In this release, the content of this table is reset. This does not impact any state history and this data isn't used by Home Assistant as of yet.

If you have no idea what this message is about, you can safely ignore it. We have merely listed this to be complete in our backward-incompatible changes report.

(@emontnemery - #52331) (history docs)

DSMR Slimme Meter

Configuring the DSMR integration via YAML has been deprecated and will be removed in Home Assistant 2021.9. If you have an existing YAML configuration for the DSMR platform is will be imported into the UI automatically on upgrade. You can safely remove the DSMR YAML configuration after upgrading Home Assistant.

(@frenck - #52179) (dsmr docs)

---

The Hourly Gas Consumption sensor has been removed from the DSMR integration. This sensor was calculated and it is not an actual datapoint from the energy meter.

If you are looking for a replacement, you can use the Derivative integration to re-create the hourly (or any other timeframe) sensor based on the total Gas consumption sensor.

(@frenck - #52147) (dsmr docs)

Google Play Music Desktop Player (GPMDP)

• The integration has been disabled since it requires an old version of the websocket-client library which is incompatible with the requirements of other integrations that are actively maintained.

• It's not clear if this integration still works with the gpmdp app that now only supports YouTube Music. If there's someone that uses the integration successfully and wants to take on the maintenance task that is required to get the integration in a compatible state, please create an issue to discuss the future of this integration.

(@MartinHjelmare - #51509) (gpmdp docs)

Growatt

The Growatt API has changed individual PV array units from Watts to Kilowatts. This change is to update the units used for these values in Home Assistant, therefore the units for these values will change.

(@muppet3000 - #52021) (growatt_server docs)

Kuler Sky

Kuler Sky lights no longer supports the deprecated white_value attribute for its lights. Use the rgbw_color attribute instead.

(@emontnemery - #52080) (kulersky docs)

MeteoAlarm

You can no longer use the 2 letters of your country code, but must now use the complete country name in your configuration. To find out which country names you can use, please look at meteoalarm.org.

(@rolfberkenbosch - #51383) (meteoalarm docs)

Modbus

As announced in 2021.4, the “old style” YAML was deprecated and now removed:

Example “old style” configuration, that is now invalid:

modbus:
  - name: hub1
    type: tcp
    host: IP_ADDRESS
    port: 502

binary_sensor:
  platform: modbus
  registers:
    - name: Sensor1
      hub: hub1
      slave: 1
      register: 100

Same configuration in valid new style:

modbus:
  - name: hub1
    type: tcp
    host: IP_ADDRESS
    port: 502
    binary_sensors:
      - name: Sensor1
        slave: 1
        address: 100

(@janiversen - #51117) (modbus docs)

---

The coil and register configuration options are changed to address and (if not default) input_type.

Previous configuration example:

modbus:
  - name: hub1
    type: tcp
    host: IP_ADDRESS
    port: 502
    covers:
      - name: Door1
        coil: 117
      - name: Door2
        register: 131
        state_open: 1
        state_closed: 0

The new configuration looks like this:

modbus:
  - name: hub1
    type: tcp
    host: IP_ADDRESS
    port: 502
    covers:
      - name: Door1
        input_type: coil
        address: 117
      - name: Door2
        address: 131
        state_open: 1
        state_closed: 0

(@janiversen - #51154) (modbus docs)

---

The configuration attributes curent_temp_register and current_temp_register_type are changed to address and input_type in order for all platforms to have a common configurations.

Before this PR, this was legal:

modbus:
  - name: hub1
    type: tcp
    host: IP_ADDRESS
    port: 502
    climates:
      - name: "Watlow F4T"
        current_temp_register: 27586
        current_temp_register_type: holding

This changes to:

modbus:
  - name: hub1
    type: tcp
    host: IP_ADDRESS
    port: 502
    climates:
      - name: "Watlow F4T"
        address: 27586
        input_type: holding

(@janiversen - #51202) (modbus docs)

---

Modbus sensor ‘reverse_order’ is no longer supported, please use ‘swap’ instead.

Old configuration:

modbus:
  - name: hub1
    type: tcp
    host: IP_ADDRESS
    port: 502
    sensors:
      - name: Sensor1
        address: 100
        reverse_order: true

New configuration:

modbus:
  - name: hub1
    type: tcp
    host: IP_ADDRESS
    port: 502
    sensors:
      - name: Sensor1
        address: 100
        swap: word

(@janiversen - #51665) (modbus docs)

---

data_count is no longer supported, please use count.

No longer supported:

modbus:
  - name: hub1
    type: tcp
    host: IP_ADDRESS
    port: 502
    climates:
      - name: "Watlow F4T"
        address: 27586
        input_type: holding
        data_count: 1
        ...

Please change it to:

modbus:
  - name: hub1
    type: tcp
    host: IP_ADDRESS
    port: 502
    climates:
      - name: "Watlow F4T"
        address: 27586
        input_type: holding
        count: 1
        ...

(@janiversen - #51668) (modbus docs)

MQTT

It's no longer possible to set attributes defined in the base component via a configured json_attributes_topic.

For example, a light no longer accepts brightness via the json_attribute_topic. This was unintended and an undocumented functionality that lead to unexpected behavior.

This change applies to all supported MQTT platforms.

(@emontnemery - #52242 #52278 #52280 #52285 #52286 #52283 #52289 #52291 #52290 #52288 #52282 #52279) (mqtt docs)

Nettigo Air Monitor

The AirQuality platform has been marked as deprecated. The air_quality entities will be deleted and replaced with sensor entities. You need to update your automations and dashboards if you have been using these air_quality entities in those.

(@bieniu - #52152) (nam docs)

Open Z-Wave

Open Z-Wave lights no longer support the deprecated white_value attribute, use rgbw_color instead.

(@emontnemery - #52063) (ozw docs)

Prometheus

Prometheus is now converting temperatures in °F to °C. If you are relying on temperature_c being in Fahrenheit, you will need to make adjustments, for example by doing a unit conversion in a PromQL query.

(@masto - #52212) (prometheus docs)

Recorder

The underlying library that is used for the database connections, has been updated. This fixes a bug, that might be a breaking change for you.

If you use an @ in your database username or password, you will have to adjust your database connection string to use %40 instead.

Database connection strings are considered URLs, thus special characters need to be encoded. %40 is the URL encoded version of @.

Rituals Perfume Genie

The switch extra state attributes fan_speed and room_size will be removed in the next release. As of this release, both attributes are available as entities, making it possible to change the value with Home Assistant.

(@milanmeu - #51993) (rituals_perfume_genie docs)

Sony Bravia TV

From April 2020, the Sony Bravia TV integration has been automatically importing your import of existing YAML configurations. Now we have removed this option for migration. Your existing configuration has been imported to the UI already and can now be safely removed from your YAML configuration files.

(@bieniu - #52141) (braviatv docs)

Spain electricity hourly pricing (PVPC)

With the change to the new, and unique, electric tariff 2.0TD, if you previously had configured multiple PVPC sensors monitoring prices for more than one of the old tariffs, only the first one will survive. This means if you have any automation or script that depends on these removed sensors, you might need to adjust them.

(@azogue - #51789) (pvpc_hourly_pricing docs)

Tasmota

Tasmota doesn't support independent control of all four channels of an RGBW light, so rgbw_color was a very poor fit for it and gave counter-intuitive results. Tasmota lights supporting color and white will now be added as a light supporting color modes hs and white, not as a light supporting color_mode rgbw. now supports setting white instead.

Scenes setting a Tasmota light can be updated by using the scene UI editor.

Automations setting a Tasmota light need to be updated manually, to set a light to white mode do:

  - service: light.turn_on
    target:
      entity_id: light.genbbc05
    data:
      white: 242

(@emontnemery - #51608) (tasmota docs)

Switcher

In preparation for multi-device support, configuration via the UI and support for discovery; this integration is migrating entity attributes into sensors to be later added as device entities. The following switch entity attributes migrated to sensors:

(@thecode - #51964) (switcher_kis docs)

Yamaha MusicCast

The integration has been rewritten from the ground up and is now configurable via the user interface only. Existing platform YAML config will automatically be imported into the user interface on upgrade and can be safely removed from the YAML configuration after the upgrade has been completed.

(@vigonotion - #51561) (yamaha_musiccast docs)

Zero-configuration networking (zeroconf)

The IPv6 configuration option has been deprecated in favor of the settings provided by the network integration.

(@bdraco - #51173) (zeroconf docs)

Abode

The previously deprecated YAML configuration of the Abode integration has been removed.

Abode 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.

(@frenck - #52357) (abode docs)

AirVisual

The Air Quality platform has been marked as deprecated, therefore the air_quality entity has been removed and replaced with sensor entities.

If you used the air_quality entity in your automations, scripts or Lovelace dashboards, you'll need to update your configuration to match this change.

(@bachya - #52349) (airvisual docs)

---

States for the "Pollutant Level" and "Main Pollutant" entities have changed; automations that depended on the old states will need to be updated.

Pollutant Level:

• Good -> good
• Moderate -> moderate
• Unhealthy -> unhealthy
• Unhealthy for sensitive groups -> unhealthy_sensitive
• Very unhealthy -> very_unhealthy
• Hazardous -> hazardous

Pollutant Label:

• Carbon Monoxide -> co
• Nitrogen Dioxide -> n2
• Ozone -> o3
• PM10 -> p1
• PM2.5 -> p2
• Sulfur Dioxide -> s2

(@bachya - #53133) (airvisual docs)

Ambient Weather Station

The previously deprecated YAML configuration of the Ambient Weather Station integration has been removed.

Ambient Weather Station 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.

(@bachya - #52459) (ambient_station docs)

AVM FRITZ!Box Net Monitor / AVM FRITZ!Box Tools

In order to optimize device load and avoid exhausting available connections, fritz_netmonitor has been merged into fritz.

Please remove your YAML existing configuration and configure the new integration.

(@chemelli74 - #52264) (fritz docs)

---

The profile switches introduced in the previous release have been removed as they where incompatible with the Home Assistant architectural design rules.

Instead, you can now block every device connected individually.

(@AaronDavidSchneider - #52721) (fritz docs)

AVM FRITZ!SmartHome

The power and energy attributes from switch entities have been removed and replaced by sensors.

If you relied on these attributes in your automations, scripts or Lovelace dashboards, you'll need to update your configuration to match this change.

(@mib1185 - #52562) (fritzbox docs)

Bosch BME280

The YAML configuration for this integration has changed. Instead of a sensor config with platform section, an integration configuration section under the integration domain key should be used.

Before:

sensor:
  - platform: bme280
    name: "Stary_Oskol"

After:

bme280:
  - name: "Stary_Oskol"

(@Kuzj - #48775) (bme280 docs)

Broadlink

The power and energy attributes from switch entities have been removed and replaced by sensors.

If you relied on these attributes in your automations, scripts or Lovelace dashboards, you'll need to update your configuration to match this change.

(@Danielhiversen - #53342) (broadlink docs)

Buienradar

The previously deprecated YAML configuration of the Buienradar integration has been removed.

Buienradar 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.

(@frenck - #52939) (buienradar docs)

CO2 Signal

The CO2 Signal integration migrated to configuration via the UI. Configuring CO2 Signal 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.

(@Danielhiversen - #53193) (co2signal docs)

Demo

Demo switch entity no longer reports current_power_w and today_energy_kwh attributes.

(@thecode - #52424) (demo docs)

devolo Home Control

The consumptions attributes from the switch entities have been removed and replaced by sensors.

If you relied on these attributes in your automations, scripts or Lovelace dashboards, you'll need to update your configuration to match this change.

(@Shutgun - #53335) (devolo_home_control docs)

GIOŚ

The Air Quality platform has been marked as deprecated, therefore the air_quality entity has been removed and replaced with sensor entities.

If you used the air_quality entity in your automations, scripts or Lovelace dashboards, you'll need to update your configuration to match this change.

(@bieniu - #52295) (gios docs)

Google Assistant

Home Assistant will no longer expose the legacy fan speeds to Google Assistant.

If you use fans with with Google Assistant, you'll need to resync your device. Ask you Google device to Sync my device or trigger an update via the google_assistant.request_sync service.

(@elupus - #53105) (google_assistant docs)

HomeKit

Previously the on/off switches provided to HomeKit by scripts, would enable or disable a script. This likely was not what is expected as Hey Siri turn on "script" would appear to do nothing.

Pressing a script switch in HomeKit now runs the script instead.

(@bdraco - #53106) (homekit docs)

HomeKit Controller

HomeKit Controller was using the wrong ID to track some sensors. The following are affected:

• Koogeek or Eve power sensors (added in Jan 2021)
• The temperature sensor added alongside homekit climate devices (added in Jul 2021, the climate entity itself is not affected)

If you have one of these you may need to remove a stale entity registry entry and you may need to fix the names of these entities as customizations may be lost.

(@Jc2k - #53848) (homekit_controller docs)

---

If you have a power sensor for a Eve Energy or Koogeek P1EU/SW2, the units for that sensor has changed from watts to W to properly follow Home Assistant standards.

(@Jc2k - #53877) (homekit_controller docs)

Honeywell Total Connect Comfort (US)

The Honeywell integration migrated to configuration via the UI. Configuring Honeywell 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.

(@rdfurman - #50731) (honeywell docs)

Huawei LTE

Routers currently in unauthenticated mode need to be provided credentials for duration of one successful startup in order to retrieve a unique id from the API. Unauthenticated mode can then be enabled for subsequent starts in integration options.

(@scop - #49878) (huawei_lte docs)

Itho Daalderop Spider

The power and energy attributes from switch entities have been removed and replaced by sensors.

If you relied on these attributes in your automations, scripts or Lovelace dashboards, you'll need to update your configuration to match this change.

(@peternijssen - #53397) (spider docs)

Jewish Calendar

The Jewish Calendar integration returned a datetime format that wasn't properly formatted according to ISO standards. This has been adjusted.

If you rely on manually parsing of dates that are returned from this integration, you might need to adjust your templates to incorporate this change.

(@frenck - #52722) (jewish_calendar docs)

Lyft

The Lyft integration has been deprecated and is pending removal in Home Assistant Core 2021.10.0. It is considered impossible to obtain API keys to be able to use this integration.

(@frenck - #53005) (lyft docs)

Mill

The consumption_today and consumption_total from the climate entity have been removed and replace by sensors.

If you relied on these attributes in your automations, scripts or Lovelace dashboards, you'll need to update your configuration to match this change.

(@Danielhiversen - #52311) (mill docs)

Modbus

All entities are set to unavailable during loading of modbus integration and remain so until data is received. Entities with scan_interval = 0 (entities without polling) are always available, to allow service calls.

The old configuration style with setting scan_interval: 9999 will cause the entity to be unavailable for 9999 seconds.

(@janiversen - #53155) (modbus docs)

MySensors

The power and energy attributes from switch entities have been removed.

If you relied on these switch attributes in your automations, scripts or Lovelace dashboards, you'll need to update your configuration to match this change.

This measurement (S_POWER, V_WATT) will still be reported as previously by the power sensor entity.

(@MartinHjelmare - #53566) (mysensors docs)

Prometheus

This includes a few changes to the names of the exported Prometheus metrics, which now better align with Prometheus naming guidelines:

• Default value for the namespace configuration variable is now homeassistant, and all metric names now have a default homeassistant_ prefix.
• Some metrics have been renamed:
• light_state renamed to light_brightness_percent.
• temperature_c renamed to climate_target_temperature_celsius.
• current_temperature_c renamed to climate_current_temperature_celsius.
• Sensor metrics now have a sensor_ name prefix.
• Temperature sensor metrics now have a _celsius unit suffix (as opposed to just _c).

Note, that users that don't currently explicitly set the namespace variable will see names changed for all exported metrics. If keeping existing metric names is important to you, you can adjust your Home Assistant and Prometheus configuration as described below.

To keep metrics exported without the homeassistant_ prefix, explicitly set an empty namespace in Home Assistant configuration:

prometheus:
  namespace: ""

To revert the other metric name changes, you can use metric_relabel_configs in your Prometheus configuration file to rename the metrics after scraping. This set of relabeling rules is a good starting point, but please note that if you set a non-empty namespace in Home Assistant you will need to adjust these rules accordingly.

(@knyar - #50156) (prometheus docs)

Rituals Perfume Genie

The previously deprecated fan speed and room size attributes have been removed. They have now have got their own entities.

(@milanmeu - #53611) (rituals_perfume_genie docs)

Synology DSM

The previously deprecated YAML configuration of the Synology DSM integration has been removed.

Synology DSM 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.

(@mib1185 - #53197) (synology_dsm docs)

Tibber

The previously deprecated YAML configuration of the Tibber integration has been removed.

Tibber 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.

(@Danielhiversen - #53235) (tibber docs)

TP-Link Kasa Smart

The power and energy attributes from switch entities have been removed and replaced by sensors. This applies to all five extra attributes about energy (current_power_w, total_energy_kwh, today_energy_kwh, voltage, current_a).

If you relied on these attributes in your automations, scripts or Lovelace dashboards, you'll need to update your configuration to match this change.

(@mib1185 - #53596) (tplink docs)

VeSync

The previously deprecated YAML configuration of the VeSync integration has been removed.

VeSync 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.

(@frenck - #52358) (vesync docs)

Viessmann ViCare

Viessmann introduced a new API to control their devices. The original (inofficial API) was shut down which rendered the Home Assistant integration useless. This breaking change restores the integrations functionality

This involves adding a new client_id parameter. It must be set with an API key from the Viessmann developer portal.

Please register and create your private API key. Follow these steps to create your API key:

1. Register and login in the Viessmann Developer Portal.
2. In the menu navigate to API Keys.
3. Create a new OAuth client using following data:

  Name: PyViCare
  Google reCAPTCHA: Disabled
  Redirect URIs: vicare://oauth-callback/everest

4. Copy the Client ID to the configuration, e.g. client_id="XXXXXXXXXXXXXX"

  vicare:
    username: VICARE_EMAIL
    password: VICARE_PASSWORD
    client_id: VICARE_CLIENT_ID

Please not that not all previous properties are available in the new API. Missing properties were removed and might be added later if they are available again.

(@oischinger - #53281) (vicare docs)

WLED

The wled.preset service has been deprecated. In the previous Home Assistant release, support for an select entity that provides access to presets has been added, use that entity in your automations and scripts instead.

(@frenck - #53383) (wled docs)

---

The playlist attribute from the WLED light entities has been removed and replaced by a playlist select entity instead of the attribute.

If you relied on the attribute in your automation or scripts, you need to adjust those to use the new entity instead.

(@frenck - #53381) (wled docs)

Xiaomi Miio

Existing Xiaomi Mi automations using the platform specific services for humidifiers will have a breaking change. You need to change their automation to use new services. Existing fan entities will be automatically replaced with new humidity entities.

The entity name is migrated from the fan entity name. The fan entity_id will change because the platform will change.

For the related entities the old fan entity name will be prepended to the new entities.

Example:

Entity with entity_id "fan.my_device" and name "My humidifier" will migrate to an entity with entity_id "humidifier.my_humidifier" and name "My humidifier".

A sensor for humidity will have a name like "My humidifier Humidity".

(@jbouwh - #52366) (xiaomi_miio docs)

Yale Smart Living

The CYale Smart Living integration migrated to configuration via the UI. Configuring Yale Smart Living 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.

(@gjohansson-ST - #50850) (yale_smart_alarm docs)

Z-Wave JS

Z-Wave JS entities will now be in an unavailable state when the parent node is considered dead by Z-Wave JS. This may impact existing automations because Home Assistant will block service calls to unavailable entities.

A node can potentially be revived by sending a ping to it, therefore you can use the new node status sensor (disabled by default) to track node status and use the zwave_js.ping_node service to try to revive the node.

The node status sensor will always be available even when the node is dead.

(@raman325 - #48017) (zwave_js docs)

Farewell to the following

The following integrations are no longer available as of this release:

• Weather Underground has been unavailable and in a non-working state and has therefore been removed. (@frenck - #52999)
• Garmin Connect has been removed. Due to API changes, it stopped working and cannot function without violating Home Assistant design rules. Garmin will not allow open source projects to their official APIs. (@cyberjunky - #52808) (garmin_connect docs)

1-Wire

The previously deprecated YAML configuration of the 1-Wire integration has been removed.

1-Wire 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.

(@epenet - #53728) (onewire docs)

AVM FRITZ!Box Tools

The attributes of the switches provided by AVM FRITZ!Box Tools have been adjusted to match the naming rules and schema of Home Assistant.

If you relied on one of these attributes in your automation or scripts, you'll need to adopt to this change.

(@AaronDavidSchneider - #54842) (fritz docs)

DSMR

The unit of measurement of gas sensors for DSMR has changed from m3 to m³.

(@bramkragten - #54110) (dsmr docs)

Epson

The previously deprecated YAML configuration of the Epson integration has been removed.

Epson 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.

(@pszafer - #55045) (epson docs)

Growatt

The previously deprecated YAML configuration of the Growatt integration has been removed.

Growatt 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.

(@frenck - #54325) (growatt_server docs)

HomeKit

The underlying HomeKit protocol version has changed from version 1.0 to version 1.1.

Cameras with motion sensors and some other accessories may need to be reset using the homekit.reset_accessory service or unpaired and paired again.

If after unpairing with your iOS the QR code does not show, the pairings can manually be removed with the homekit.unpair service using the Developer Tools.

(@bdraco - #53780) (homekit docs)

HomeKit Controller

A future release (currently scheduled for 2021.12.0) will remove the (deprecated) air quality platform from the HomeKit Controller integration.

Starting from this release the air quality values have been broken out as their own sensors, making them easier to incorporate in your dashboard widgets, graphs and automations.

If you relied on an air quality entity (provided by the HomeKit Controller integration) in your automation or scripts, you'll need to adopt to this change.

(@Jc2k - #54673) (homekit_controller docs)

IKEA TRÅDFRI

The legacy code, which imported hosts from a JSON file have been removed. If you relied on that, please follow the instructions to setup the hosts (can be detected automatically).

To avoid this, upgrade to 2021.8.x first (which will automatically import the hosts from the JSON file) and then upgrade to latest release.

(@janiversen - #54452) (tradfri docs)

Lutron

If (and only if) you currently attempt to make use of the (previously ambiguous) Lutron button events in an automation, then you will need to switch to the new, unambiguous name. That said, since the current events are ambiguous they are not very useful.

(@nickovs - #53666) (lutron docs)

MQTT

MQTT fan no longer supports the legacy speeds (OFF, LOW, MEDIUM, HIGH). With release 2021.3 the support for legacy speeds was announced to be removed after a quarter (2021.7).

With removing the legacy speeds support, integrations that rely on MQTT fan platform that still use legacy speeds would break because they can not be setup if deprecated attributes are used. This includes the MQTT auto discovery.

To prevent that these integrations will fail to setup, the deprecated attributes listed here are still allowed in the config:

• payload_high_speed
• payload_low_speed
• payload_medium_speed
• speed_command_topic
• speeds
• speed_state_topic
• speed_value_template

(@jbouwh - #54768) (mqtt docs)

The last_reset_topic configuration variable for MQTT sensor is deprecated, last_reset_value_template is still supported but will use the state_topic if no last_reset_topic is configured.

In Home Assistant core 2021.10, it will no longer be possible to configure a last_reset_topic.

(@emontnemery - #55463) (mqtt docs)

MySensors

MySensors lights no longer supports deprecated white_value, use rgbw_color instead.

(@emontnemery - #52068) (mysensors docs)

Nanoleaf

The Nanoleaf integration migrated to configuration via the UI. Configuring Nanoleaf 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.

If you have configured Nanoleaf with the discovery integration: You can remove discovery: from your YAML configuration if you only used it for Nanoleaf. The .nanoleaf.conf file in your configuration folder is no longer used, you can delete it after upgrading.

(@milanmeu - #52199) (nanoleaf docs)

Nmap Tracker

The Nmap Tracker integration migrated to configuration via the UI. Configuring Nmap Tracker 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.

To disable creation of new entities, use the the system option to disable new entities for the config entry, and manually enable entities as needed.

(@bdraco - #54715) (nmap_tracker docs)

OVO Energy

These attributes have been removed and replaced with full sensors for both gas and electricity:

• start_time
• end_time

If you relied on one of these attributes in your automation or scripts, you'll need to adopt to this change.

(@timmo001 - #54952) (ovo_energy docs)

Rainforest Eagle-200

The Rainforest Eagle-200 integration migrated to configuration via the UI. Configuring Rainforest Eagle-200 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.

(@balloob - #54846) (rainforest_eagle docs)

SimpliSafe

SimpliSafe locks no longer have a jammed attribute; instead, when jammed, they will show a jammed state.

If you are currently using the jammed attribute in your automation or scripts, you'll need to adapt them to this change.

(@bachya - #54006) (simplisafe docs)

Smappee

The power and energy attributes from switch entities have been removed and replaced by sensors.

If you relied on these attributes in your automations, scripts or Lovelace dashboards, you'll need to update your configuration to match this change.

(@bsmappee - #54329) (smappee docs)

Solar-Log

The Watt-peak unit of measurement has changed to W.

(@Ernst79 - #55110) (solarlog docs)

Supervisor

The usage of "snapshot" is deprecated, from now "backup" is used instead.

• The service snapshot_full is now named backup_full, the service snapshot_full will be removed in Home Assistant 2021.11.
• The service snapshot_partial is now named backup_partial, the service snapshot_partial will be removed in Home Assistant 2021.11.
• Using snapshot in the data for the restore_full and restore_partial services is deprecated and will be removed in Home Assistant 2021.11, use slug instead.

Old examples:

service: hassio.snapshot_full
data:
  name: "Awesome full snapshot"
...
service: hassio.snapshot_partial
data:
  name: "Awesome partial snapshot"
  addons:
    - awesome_addon
...
service: hassio.restore_full
data:
  snapshot: sn2321
...
service: hassio.restore_partial
data:
  snapshot: sn2321
  addons:
    - awesome_addon

New examples:

service: hassio.backup_full
data:
  name: "Awesome full snapshot"
...
service: hassio.backup_partial
data:
  name: "Awesome partial snapshot"
  addons:
    - awesome_addon
...
service: hassio.restore_full
data:
  slug: sn2321
...
service: hassio.restore_partial
data:
  slug: sn2321
  addons:
    - awesome_addon

(@ludeeus - #53851) (hassio docs) (zwave_js docs)

Tesla Powerwall

The Tesla Powerwall attributes for energy_exported_(in_kW) and energy_imported_(in_kW) have been converted to their own energy sensors.

If you relied on those attributes in your automation or scripts, you'll need to adapt them to this change.

(@bdraco - #54018) (powerwall docs)

Toon

The unit of measurement of gas and water sensors for Toon has changed from m3 to m³.

(@bramkragten - #54110) (toon docs)

UpCloud

The previously deprecated YAML configuration of the UpCloud integration has been removed.

UpCloud 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.

(@scop - #54516) (upcloud docs)

Uptime Robot

The Uptime Robot integration migrated to configuration via the UI. Configuring Uptime Robot 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.

(@ludeeus - #53938) (uptimerobot docs)

Wink

The Wink integration has been deprecated and is pending removal in Home Assistant 2021.11.

Their developer portal, needed for obtaining an API token, has been taken offline and their customer support has confirmed no new token or client/secret can be obtained. This makes it impossible to use this integration.

(@frenck - #54496) (wink docs)

Xiaomi Miio

The following fan entity attributes temperature, humidity, aqi, purify volume, filter life remaining, filter hours used, co2, illuminance, motor speed and motor2 speed have been migrated to their own sensor entities.

If you relied on those attributes in your automation or scripts, you'll need to adapt them to this change.

The filter_rfid_product_id and filter_rfid_tag fan entity attributes have been removed as they are of little use to keep around.

(@bieniu - #54564) (xiaomi_miio docs)

---

The service fan_set_led_brightness is removed and the Led Brightness select entity has been created instead.

If you relied on this service in your automation or scripts, you'll need to adapt them to this change.

(@bieniu - #54702) (xiaomi_miio docs)

---

The previously (deprecated and old style) speeds, speed list and speed services have been removed.

(@SmaginPV - #54182) (xiaomi_miio docs)

---

The services fan_set_buzzer_on, fan_set_buzzer_off, fan_set_led_on, fan_set_led_off, fan_set_child_lock_on, fan_set_child_lock_off, fan_set_auto_detect_on, fan_set_auto_detect_off, fan_set_learn_mode_on and fan_set_learn_mode_off have been removed.

Switch entities have been created to replace those.

If you relied on one of these services in your automation or scripts, you'll need to adapt them to this change.

(@bieniu - #54834) (xiaomi_miio docs)

---

The previously deprecated YAML configuration of the Xiaomi Miio integration has been removed (with the exception of the remote platform).

Xiaomi Miio 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.

(@rytilahti - #54930) (xiaomi_miio docs)

---

The services fan_set_favorite_level, fan_set_fan_level, and fan_set_volume have been removed and number entities have been created instead.

If you relied on one of these services in your automation or scripts, you'll need to adapt them to this change.

(@bieniu - #54977) (xiaomi_miio docs)

Z-Wave JS

The Basic CC always comes with two values, currentValue and targetValue.

We currently only have a discovery schema for currentValue which creates a sensor, making these Basic CC values noninteractive. As of this release we will create a number platform entity for Basic CC values instead of sensors.

(@raman325 - #54512) (zwave_js docs)

---

If you have created an automation with the zwave_js device condition Current value of a Z-Wave Value for the CONFIGURATION Command Class, your automation will no longer work.

Instead, you should use the Config parameter device condition for the value you were trying to use for your condition.

(@raman325 - #54962) (zwave_js docs)

Custom integrations: Cameras

This breaking change is only relevant to custom integration authors!

The function signature for async_camera_image and camera_image has changed to include a width and height.

    async def async_camera_image(
        self, width: int | None = None, height: int | None = None
    ) -> bytes | None:

The goal of the change is to reduce the overhead of sending large images that will only be displayed as small images as this can quickly consume hundred of megabytes of bandwidth / mobile data allocation. Scaling should be done on a best effort basis and is not a strict requirement as the existing behavior of falling back to scaling at the display layer is preserved.

• Integrations should pass on the width and height if the underlying camera is capable of scaling the image.

• Integrations may choose to ignore the height parameter in order to preserve aspect ratio

• If the integration cannot scale the image and returns a jpeg image, it will automatically be scaled by the camera integration when requested.

(@bdraco - #53835)

Custom integrations: Sensors

This breaking change is only relevant to custom integration authors!

Although not a breaking change from a user's perspective, this is a significant change from a developer's perspective.

Temperature conversions are moving from the Entity base class to the SensorEntity base class.

Additionally, we have two new properties, native_value (which replaces state) and native_unit_of_measurement which replaces unit_of_measurement.

Read all about it in the developer blog:

https://developers.home-assistant.io/blog/2021/08/12/sensor_temperature_conversion/

(@emontnemery - #48261) (abode docs) (sensor docs)

---

Additionally, a new sensor state class has been introduced: total_increasing.

This changes the measurement state class that was used in conjunction with the last_reset attribute. For more information about his can be found in the developer blog about it:

https://developers.home-assistant.io/blog/2021/08/16/state_class_total/

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:

• acos
• as_timestamp
• asin
• atan
• atan2
• cos
• float
• log
• multiply
• round
• sin
• sqrt
• strptime
• tan
• timestamp_custom
• timestamp_local
• timestamp_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)

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-acrobat
• adobe
• amazon-alexa
• amazon
• android-auto
• android-debug-bridge
• bandcamp
• battlenet
• blogger
• buffer
• cash-usd-outline
• cash-usd
• cellphone-android (alternative: cellphone)
• cellphone-iphone (alternative: cellphone)
• concourse-ci
• currency-usd-circle
• currency-usd-circle-outline
• do-not-disturb-off (alternative: minus-circle-off)
• do-not-disturb (alternative: minus-circle)
• douban
• file-pdf (alternative: file-pdf-box)
• file-pdf-outline (alternative: file-pdf-box)
• file-pdf-box-outline (alternative: file-pdf-box)
• google-photos
• home-currency-usd
• laptop-chromebook (alternative: laptop)
• laptop-mac (alternative: laptop)
• laptop-windows (alternative: laptop)
• microsoft-edge-legacy
• microsoft-yammer
• pdf-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)
• telegram
• untappd
• vk
• xamarian-outline
• xing
• y-combinator

The following icons have been renamed:

• apple-airplay to cast-variant
• application to application-outline
• application-cog to application-cog-outline
• application-settings to application-settings-outline
• bolnisi-cross to cross-bolnisi
• boom-gate-up to boom-gate-arrow-up
• boom-gate-up-outline to boom-gate-arrow-up-outline
• boom-gate-down to boom-gate-arrow-down
• boom-gate-down-outline to boom-gate-arrow-down-outline
• buddhism to dharmachakra
• cellphone-erase to cellphone-remove
• celtic-cross to cross-celtic
• christianity to cross
• christianity-outline to cross-outline
• face to face-man
• face-outline to face-man-outline
• face-profile-woman to face-woman-profile
• face-shimmer to face-man-shimmer
• face-shimmer-outline to face-man-shimmer-outline
• flash-circle to lightning-bolt-circle
• floor-lamp-variant to floor-lamp-torchiere-variant
• gif to file-gif-box
• gradient to gradient-vertical
• hand to hand-front-right
• hand-left to hand-back-left
• hand-right to hand-back-right
• hinduism to om
• human-greeting to human-greeting-variant
• iframe to application-brackets
• iframe-outline to application-brackets-outline
• iframe-array to application-array
• iframe-array-outline to application-array-outline
• iframe-braces to application-braces
• iframe-braces-outline to application-braces-outline
• iframe-parentheses to application-parentheses
• iframe-parentheses-outline to application-parentheses-outline
• iframe-variable to application-variable
• iframe-variable-outline to application-variable-outline
• islam to star-crescent
• judaism to star-david
• monitor-clean to monitor-shimmer
• pharmacy to mortar-pestle-plus
• sparkles to shimmer
• teach to human-male-board
• television-clean to television-shimmer
• text-subject to text-long
• twitter-retweet to repeat-variant
• voice-off to account-voice-off

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)

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)

Discovery API

The API endpoint /api/discovery_info now only return blank values. This endpoint is scheduled to be removed in Home Assistant Core 2022.1.

As a regular user of Home Assistant, this change should not affect you.

(@ludeeus - #56097) (api docs)

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)

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.

(@bdraco - #55860)

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)

Minut Point

The (non-working) pressure sensor has been removed.

(@fredrike - #56934) (point docs)

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)

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)

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)

Network UPS Tools (NUT)

The extra attribute state is removed from all sensors, since it is already exposed as an own sensor.

If you relied on this attribute for your automations or script, you might need to adjust to this change.

(@mib1185 - #56078) (nut docs)

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.

(@Danielhiversen - #56829) (opengarage docs)

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)

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.

(@bachya - #55426) (recollect_waste docs)

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)

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)

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.

(@engrbm87 - #55642) (speedtestdotnet docs)

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.

(@Danielhiversen - #56209) (surepetcare docs)

System Bridge

The following additional state attributes have been removed from the existing sensors:

• available
• filesystem
• load_average
• load_idle
• load_system
• load_user
• mount
• size
• type
• used

You should update any automations and scripts that depend on these state attribute to use the separate sensors available for these states.

(@timmo001 - #53892) (system_bridge docs)

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)

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)

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)

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)

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)

Custom integrations: ruamel.yaml

The unused ruamel.yaml utility functions have been removed. They were never in use nor documented. If your custom integration relied on ruamel.yaml being installed, make sure it's part of your manifest.

(@balloob - #55672)

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)

All Service Calls

Entities that are now shown on the device page on the configuration or diagnostic section, will no longer be targeted and called by service calls that target the specific device or area the device or entity is in.

If you need to make a service call to these entities, you will need to call them by their entity ID explicitly.

Please note: This does not apply to entity groups, as groups are explicitly based on entities (unlike areas) and thus still work as before.

(@emontnemery - #57671)

Amazon Alexa / Google Assistant

Entities that are now shown on the device page on the configuration or diagnostic section, will no longer be exposed by default to Amazon Alexa or Google Assistant.

If you want to expose these entities, you'll need to expose them explicitly.

(@emontnemery)

Recorder / Databases

The Home Assistant project has now explicitly defined a set of databases that are supported by the recorder.

We now support the following databases:

• MariaDB ≥ 10.3
• MySQL ≥ 8.0
• PostgreSQL ≥ 12
• SQLite ≥ 3.32.1

All other databases and database versions are now deprecated.

If your used or configured database doesn't match any of the above requirements, a warning will be logged. As of Home Assistant 2022.1, the recorder will no longer connect to an unsupported database.

(@emontnemery - #58161) (recorder docs)

---

It is no longer possible to filter out state_changed events from the recorder's event_types exclude filter.

A warning will be logged in Home Assistant Core 2021.11 and the configuration will be rejected in Home Assistant Core 2022.2.

Python 3.8: Deprecation warning

Python 3.8 has been deprecated because Python 3.10 has been released. Support will be dropped in Home Assistant 2022.1.

Support for Python 3.10 hasn't completed yet, however we aim to complete that before the 3.8 deprecation period has ended. It is advised to upgrade to Python 3.9 at this point.

If you run Home Assistant OS, Supervised or the Container installation type: No action is required from your end, we will take care of this for you.

(@balloob - #57079)

Aurora ABB Solar PV

The Aurora ABB Solar PV integration migrated to configuration via the UI. Configuring Aurora ABB Solar PV 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.

(@davet2001 - #36300) (aurora_abb_powerone docs)

AVM FRITZ!Box Tools

AVM FRITZ!Box Tools services now ask for a device_id and no longer for an entity_id. Please review your automation and scripts accordingly.

(@chemelli74 - #58005) (fritz docs)

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; Please check the integrations configuration page for imported DLNA-DMR configuration. Once it has been migrated, it can be safely removed from your YAML configuration.

(@chishm - #56886) (dlna_dmr docs)

Efergy

The Efergy integration has been migrated to configuration via the UI. Configuring Efergy 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.

Additionally, the following sensor names have changed:

• Energy Usage is now Power Usage.
• Any configured energy period, for example, monthly was Energy Consumed is now Monthly Consumption.
• Any configured cost period, for example, monthly was Energy Cost is now Monthly Energy Cost.
• Per-Device Usage is now Power Usage with the sensor id trailing.

(@tkdrob - #56890) (efergy docs)

Environment Canada

The Environment Canada integration has been migrated to configuration via the UI. Configuring Environment Canada 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.

Additionally, non-loop radar images are no longer supported; Sensor entities now have the location of the station as a part of the sensor's entity name.

(@gwww - #57127) (environment_canada docs)

Flux LED/MagicLight

The Flux LED integration has been migrated to configuration via the UI. Configuring Flux LED 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.

(@icemanch - #56354) (flux_led docs)

HomeKit

The previously deprecated HomeKit configuration options safe_mode, zeroconf_default_interface, and auto_start have now been removed.

If you still have these options in your YAML configuration, you must be remove them from your YAML configuration.

(@bdraco - #58320)

Input Select / Dropdown Helper

When the option list of a Dropdown helper / input_select is updated, it will try to maintain the currently selected option, if the selected option also is present in the new options provided; otherwise it will reset to the first option from the newly provided list.

Previously, when a new list of options was provided, it would always reset to the first item of the list.

(@frenck - #53334) (input_select docs)

IQVIA

Previously, IQVIA supported long-term statistics for the Asthma Index: Tomorrow sensor. This is incorrect: long-term statistics are meant for actual, current measurements (not future forecasts). Therefore, long-term statistics support has been removed for this sensor.

(@bachya - #57687) (iqvia docs)

Itho Daalderop Spider

The Itho Daalderop Spider integration previously migrated to configuration via the UI. Configuring Itho Daalderop Spider 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 thus can be safely removed from your YAML configuration after upgrading.

(@peternijssen - #57974) (spider docs)

Microsoft text-to-speech (TTS)

The default voice is changed to JennyNeural; The previous default ZiraRUS (Standard Voice) is no longer supported in eastus or any other region that has rolled out GA neural voices as Standard voices become deprecated.

(@tylergibson - #58499) (microsoft docs)

OctoPrint

The OctoPrint integration migrated to configuration via the UI. Configuring OctoPrint 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.

The following sensors have been removed:

• sensor.<printer>_time_remaining
• sensor.<printer>_time_elapsed

The following sensors have been added:

• sensor.octoprint_start_time
• sensor.octoprint_estimated_finish_time

(@rfleming71 - #58040) (octoprint docs)

OpenGarage

The attributes (wifi_signal and distance_sensor) for OpenGarage covers are removed and replaced by individual sensors.

Also, door_state is removed as an attribute, but you can use the state directly instead.

Please update any automations or scripts that depend on the removed attributes.

(@Danielhiversen - #57976) (opengarage docs)

OpenZWave

The OpenZWave (ozw) integration is being marked as deprecated. The upstream project is not currently being maintained, and has not reached stable status.

We recommend transitioning to the Z-Wave JS integration.

While the integration is not currently slated for removal, it will no longer be receiving updates and may be removed at a later date.

See the Z-Wave JS migration documentation for more information.

Pentair ScreenLogic

Screenlogic lights have moved to the light platform. The switches that previously represented these lights will need to manually be deleted in Configuration >> Entities. If you are using these switch entities in your automation or scripts, you will need to update those to use the new light entities instead.

The state is now refreshed with a short delay to ensure the toggles do not flip/flop between states as the controller takes ~600ms to make the change.

(@bdraco - #55467) (screenlogic docs)

Phone Modem

The sensor state attributes of modem_callerid integration are now only populated when the values are known.

If you use these attributes in your automations or scripts, you'll need to adjust those to be able to handle missing attributes.

(@tkdrob - #57774) (modem_callerid docs)

Rainforest Eagle

The previously deprecated YAML configuration of the Rainforest Eagle integration has been removed.

Rainforest Eagle 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.

(@frenck - #57636) (rainforest_eagle docs)

RainMachine

RainMachine services have been reorganized and now utilize a Home Assistant target (entity ID) or selector (device ID) instead of using an internal RainMachine identifier.

Additionally, services are restricted to only the targets that apply:

Device Services (i.e., must be provided a device ID)

• pause_watering
• stop_all
• unpause_watering

Entity Services (i.e., must be provided an associated switch entity ID [either a program or a zone])

• disable_program
• disable_zone
• enable_program
• enable_zone
• start_program
• start_zone
• stop_program
• stop_zone

(@bachya - #57145) (rainmachine docs)

Renault

The last_update state attribute has been moved to a stand-alone entity (and dropped from battery and location entities). If you used this attribute in your scripts or automations; you'll need to adjust those to this change.

(@epenet - #57750) (renault docs)

SimpliSafe

SimpliSafe requires a new web-based authentication method. When starting up, Home Assistant will automatically prompt you to re-authorize your instance.

(@bachya - #57212) (simplisafe docs)

SolarEdge

The SolarEdge integration now provides unique IDs for its entities, so the entities are now visible and customizable in the Home Assistant frontend.

Some names have been corrected as they had incorrect descriptions. This may cause some of your entity IDs provided by SolarEdge to have changed this release.

In case you have been using these entities in your automations, scripts, or dashboards, you can either rename those entity IDs to the old entity ID or adjust the places you've used them accordingly.

Additionally, if a sensor you used disappeared, it might have been disabled by default during upgrade. Please be sure to check if the entity is enabled in that case.

(@terminet85 - #55902) - (@purcell-lab - #58773)

Sonos

The sonos.set_option service has been removed and replaced with individual switch entities which both control the features and display if currently enabled.

The night_sound and speech_enhance attributes on the Sonos media_player entities are also removed.

If you are using those in your automations or scripts, you'll need to replace these with the new switch entities.

(@jjlawren - #54502) (sonos docs)

Stookalert

The Stookalert integration has been migrated to configuration via the UI. Configuring Stookalert 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.

(@frenck - #57119) (stookalert docs)

Supervisor

The 2021.09 release deprecated the usage of "snapshot" in the Supervisor (hassio) integration and was scheduled to be removed in 2021.11, that is now.

Old services and service data that contained "snapshot" has now been removed, and you need to update your configuration if you use any of these to continue to use it.

If you used the snapshot argument for the restore services you now have to replace that with slug

Example:

# Old name
service: hassio.restore_full
data:
  snapshot: sn2321

# New name
service: hassio.restore_full
data:
  slug: sn2321

(@ludeeus - #57652) (hassio docs)

UptimeRobot

The previously deprecated YAML configuration of the UptimeRobot integration has been removed.

UptimeRobot 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.

(@ludeeus - #57761) (uptimerobot docs)

Utility Meter

The offset parameter for utility_meter sensors is now limited to at most 27 days. If you used more then 27 days you must now migrate to cron.

(@dgomes - #55625) (utility_meter docs)

Venstar

The Venstar integration migrated to configuration via the UI. Configuring Venstar 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.

The humidifer and timeout options have been removed, and thus ignored when importing your YAML configuration into the UI.

(@garbled1 - #58152) (venstar docs)

Viessmann ViCare

Due to upstream library updates, a breaking change was introduced that required changes to sensor and binary_sensor entities.

Circuit, Burner and Compressor have been separated out from the "main" device. Multiple circuits and burners now allow "duplicate sensors", we've added the circuit or burner number as suffix.

Most of you should not see a difference, but complex installations (with more than one circuit and/or burner), will have multiple entities, suffixed with their burner or entity IDs.

For example, if you have two circuits instead of a single climate.vicare entity you will now instead have two entities:

• climate.vicare_1
• climate.vicare_2

This will provide you more control, but requires you to adapt your existing scripts and automations to use the new entity IDs.

The same has been done for sensor, binary_sensor and water_heater entities.

Also, note that binary sensors might be created twice since the unique IDs for those entities have changed. Please remove the old disabled binary_sensor entities, in case you encounter this.

(@oischinger - #57700) (vicare docs)

VLC media player Telnet

The VLC media player Telnet integration migrated to configuration via the UI. Configuring VLC media player Telnet 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.

(@MartinHjelmare - #57513) (vlc_telnet docs)

Xiaomi Miio

Attributes from the vacuum entities have been replaced with sensors.

This means that all your references to these attributes must be replaced with its sensor in your automations, scripts and dashboards.

Some sensors have been disabled by default and need manual enablement, once the integration has been set up. For example, the attribute mop_attached: true has now been replaced with binary_sensor.<NAME>_mop_attached.

(@OGKevin - #54990) (xiaomi_miio docs)

Yeelight

The option to override the Yeelight model will only appear if the detected model is not in the database. Otherwise, it will be hidden.

(@bdraco - #56967) (yeelight docs)

Farewell to the following

The following integrations are no longer available as of this release:

• Essent has been removed. The API is no longer usable for this integration and has therefore been removed. (@TheLastProject - #56991)
• Lyft has been previously deprecated and now removed. API keys are no longer being provided. (@frenck - #57638)
• Nello has been removed. The services are no longer available, and have been offline for over 6 months. (@pattyland - #57926)
• Huawei Router has been removed. It relies on web scraping, which is no longer allowed. (@yuvalabou - #57136)
• Wink has been previously deprecated and now removed. (@frenck - #57634)

customize.yaml UI (customization)

The customize.yaml UI (customization) has been removed. The YAML configuration for this is recommended and remains available. To customize entities, use the entity settings available via the icon in the top right of the entity "more info" dialog (when clicking on an entity). Entity settings now also allows customizing device_class for certain binary_sensor and cover cases.

A small explanation why it has been removed:

With customize, one is changing the state machine directly, without any checks. This comes at a risk. Additionally, for many use cases (like: name, icon, device class) one should edit the entity via the UI instead, which is possible for the greater part of the entities nowadays.

The old customize UI is confusing in many ways and has a level of power that, if wielded incorrectly, can have unforeseen consequences. Someone found and used the customize UI first, and then things are out of sync throughout the UI, as the internal entity registry would show the old values.

The customize UI also relied on setting up an include and YAML configuration to begin with; which already made it an advanced feature.

Therefore, the customize UI was removed and remains available as an advanced YAML feature, additionally we have added the capability, to adjust the common device_class changes using the "Show as" feature while editing the entity from UI.

Add-ons, Backups & Supervisor

The Supervisor panel has been merged into the configuration panel. The separate menu item from the sidebar has been removed.

---

The binary_sensor with "running" device_class that was provided for the Home Assistant Operating System device did not work and has now been removed; If you have added this to templates or automations, remove it from your configuration.

(@ludeeus - #60597) (hassio docs)

Companion App

The Companion App configuration has been merged into the configuration panel. The separate menu item from the sidebar has been removed.

Advantage Air

The HVAC mode for zone climate entities was set to FAN or OFF, because the actual HVAC mode is set for the entire ducted AC system. However, using FAN means the Google Home app won't let you set a target temperature, so it has been changed to AUTO instead.

(@Bre77 - #52816) (advantage_air docs)

BMW ConnectedDrive

The following services/sensors have been removed due to not being available using the My BMW API:

• alltrips_*
• lasttrips_*
• chargingconnectiontype
• charginginductivepositioning
• lastchargingendreason
• lastchargingendresult
• maxelectricrange

Attributes of binary_sensor.doors and binary_sensor.windows do not start with door/window anymore.

notify requires a location attribute at data.location, as the MyBMW API only supports sending POI and not messages.

The find_vehicle service will always send the location of your Home Assistant instance to BMW.

(@rikroe - #59881 #60938) (bmw_connected_drive docs)

Brunt Blind Engine

The Brunt integration migrated the connection settings to configuration via the UI. Configuring the connection to the Brunt API via YAML configuration has been deprecated and will be removed in a future Home Assistant release.

Your existing connection YAML configuration is automatically imported on upgrade to this release; and thus can be safely removed from your YAML configuration after upgrading.

Additionally, the Brunt integration can now be reloaded via the Integrations screen in the frontend and will also reload if a Brunt device is removed from your account.

(@eavanvalkenburg - #49714) (brunt docs)

Fronius

The Fronius integration migrated to configuration via the UI. Configuring Fronius 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.

This change will remove manual configuration of Fronius device IDs. Connected SolarNet devices will be detected automatically on startup.

(@farmio - #59686) (fronius docs)

Guardian

Guardian services have been reorganized and now utilize a Home Assistant selector (device ID) instead of using a Guardian entity.

(@bachya - #58632) (guardian docs)

HomeKit Controller

This release removes the air quality from HomeKit Controller as the platform has been previously deprecated.

The air quality values have been broken out as their own sensors starting from September, making them easier to incorporate in your dashboard widgets, graphs, and automations. These should be used instead.

(@Jc2k - #60480) (homekit_controller docs)

Hue

Events for Hue remotes/switches

Philips/Signify streamlined the events that are emitted for remotes/switches; these are now no longer device specific but more generic. This means that if you're relying on the hue_event to trigger events emitted by these devices, the event_data will now be slightly different. To easily identify what events get emitted by your Hue remotes, Open Developer Tools and subscribe to the hue_event.

Light entities for Hue rooms/zones

Entities for Hue groups (zones/rooms) will be imported but in a disabled state by default. The Integration option to enable Hue groups has been phased out in favor of the default Home Assistant functionality to enable/disable entities.

To enable any (new) light entities for Hue groups: Open settings --> integrations --> Hue --> Entities --> Click one of the disabled entities and enable it.

Existing Hue group lights for rooms/zones will be migrated as enabled entities.

Legacy Hue groups of type LightGroup (which are not visible in the official Hue app) will no longer be supported!

Entities for Hue scenes

If you create any scenes for your Hue zones/rooms, these will now be automatically imported to Home Assistant as scene entity, including support for the new Hue Dynamic Scenes. You can disable any scene entities you don't like to use in Home Assistant (or delete them in the Hue app).

(@marcelveldt - #58996) (hue docs)

KNX

The KNX integration migrated the connection settings to configuration via the UI. Configuring the connection to the KNX bus via YAML configuration has been deprecated and will be removed in a future Home Assistant release.

Your existing connection YAML configuration is automatically imported on upgrade to this release; and thus can be safely removed from your YAML configuration after upgrading.

Additionally, the KNX integration can now be reloaded via the Integrations screen in the frontend, and thus the knx.reload service has been removed.

(@marvin-w - #59377) (knx docs)

---

The last_knx_update attribute has been removed from the KNX sensors and binary sensors. The last_update attribute can be used alternatively.

If you are relying on this attribute in your automations or script, you will need to adjust them to this change.

(@farmio - #58786) (knx docs)

---

The configuration key event_filter is now deprecated and will be removed in a future version of Home Assistant. Please use the new event config key instead.

(@farmio - #57621) (knx docs)

Kostal Plenticore

The "Battery Strategy" sensor has been removed from the Kostal Plenticore integration. It is replaced by a switch and a select entity to allow setting the battery charging settings from Home Assistant.

(@slowflyer - #56529) (kostal_plenticore docs)

Litter-Robot

The litterrobot.reset_waste_drawer and litterrobot.set_wait_time services are deprecated and replaced by dedicated button entities; please use those instead.

(@natekspencer - #59734) (litterrobot docs)

Material Design Icons (MDI)

The previously deprecated MDI icons, now have been removed.

The following icons have been removed:

• adobe-acrobat
• adobe
• amazon-alexa
• amazon
• android-auto
• android-debug-bridge
• bandcamp
• battlenet
• blogger
• buffer
• cash-usd-outline
• cash-usd
• cellphone-android (alternative: cellphone)
• cellphone-iphone (alternative: cellphone)
• concourse-ci
• currency-usd-circle
• currency-usd-circle-outline
• do-not-disturb-off (alternative: minus-circle-off)
• do-not-disturb (alternative: minus-circle)
• douban
• file-pdf (alternative: file-pdf-box)
• file-pdf-outline (alternative: file-pdf-box)
• file-pdf-box-outline (alternative: file-pdf-box)
• google-photos
• home-currency-usd
• laptop-chromebook (alternative: laptop)
• laptop-mac (alternative: laptop)
• laptop-windows (alternative: laptop)
• microsoft-edge-legacy
• microsoft-yammer
• pdf-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)
• telegram
• untappd
• vk
• xamarian-outline
• xing
• y-combinator

The following icons have been renamed:

• apple-airplay to cast-variant
• application to application-outline
• application-cog to application-cog-outline
• application-settings to application-settings-outline
• bolnisi-cross to cross-bolnisi
• boom-gate-up to boom-gate-arrow-up
• boom-gate-up-outline to boom-gate-arrow-up-outline
• boom-gate-down to boom-gate-arrow-down
• boom-gate-down-outline to boom-gate-arrow-down-outline
• buddhism to dharmachakra
• cellphone-erase to cellphone-remove
• celtic-cross to cross-celtic
• christianity to cross
• christianity-outline to cross-outline
• face to face-man
• face-outline to face-man-outline
• face-profile-woman to face-woman-profile
• face-shimmer to face-man-shimmer
• face-shimmer-outline to face-man-shimmer-outline
• flash-circle to lightning-bolt-circle
• floor-lamp-variant to floor-lamp-torchiere-variant
• gif to file-gif-box
• gradient to gradient-vertical
• hand to hand-front-right
• hand-left to hand-back-left
• hand-right to hand-back-right
• hinduism to om
• human-greeting to human-greeting-variant
• iframe to application-brackets
• iframe-outline to application-brackets-outline
• iframe-array to application-array
• iframe-array-outline to application-array-outline
• iframe-braces to application-braces
• iframe-braces-outline to application-braces-outline
• iframe-parentheses to application-parentheses
• iframe-parentheses-outline to application-parentheses-outline
• iframe-variable to application-variable
• iframe-variable-outline to application-variable-outline
• islam to star-crescent
• judaism to star-david
• monitor-clean to monitor-shimmer
• pharmacy to mortar-pestle-plus
• sparkles to shimmer
• teach to human-male-board
• television-clean to television-shimmer
• text-subject to text-long
• twitter-retweet to repeat-variant
• voice-off to account-voice-off

MQTT

The following previously deprecated MQTT fan options are no longer supported and have been removed:

• payload_high_speed
• payload_low_speed
• payload_medium_speed
• speed_command_topic
• speed_list
• speed_state_topic
• speed_value_template

(@jbouwh - #58992) (mqtt docs)

Notifications for Android TV

The Notifications for Android TV integration allows you to send custom notifications to Android TV devices. Sending a file along with the notification, allows you to send image files that will show up above the notification.

Now that support for icons has been added in the same way as images, the file option has been renamed to image to properly identify what you're sending with the notification.

As such, code and automations that use the file option for an image have to refer to image from now on.

(@redahb - #60159) (nfandroidtv docs)

Pentair ScreenLogic

Screenlogic SCG levels have moved to the number platform to support setting of these values. The sensor entities that previously represented these values will need to be manually deleted in Configuration -> Entities.

(@dieselrabbit - #60872) (screenlogic docs)

Phone Modem

The previously deprecated YAML configuration of the Phone Modem integration has been removed. Phone Modem 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.

(@tkdrob - #59526) (modem_callerid docs)

RainMachine

The rainmachine.disable_program, rainmachine.enable_program, rainmachine.disable_zone, and rainmachine.enable_zone services have been removed.

Instead, new configuration switches related to each entity can be used to enable/disable the program/zone.

(@bachya - #59617) (rainmachine docs)

Renault

The renault.charge_start service is deprecated and replaced by a dedicated start charge button entity; please use that entity to start the charge instead.

(@epenet - #59383) (renault docs)

SimpliSafe

SimpliSafe services have been reorganized and now utilize a Home Assistant selector (device ID) instead of using a SimpliSafe system ID.

(@bachya - #58722) (simplisafe docs)

SMA Solar

Previously when the inverter was not supplying any power, the sensors showed as Unknown. These sensors will now show the value of 0, making it more useful for graphs or calculations.

(@rklomp - #59848) (sma docs)

Sonos

The sonos.set_option service has been removed along with the bass_level and treble_level attributes on media_player entities.

Controls for bass and treble adjustments have been moved to dedicated number entities.

(@jjlawren - #60498) (sonos docs)

Statistics

All statistical characteristics were removed from sensor attributes and are now selectable through state_characteristic as the state of the sensor. The parameter state_characteristic will become mandatory in a future release.

Please adapt the configuration of your statistics sensor(s) and expose the characteristic you are interested in directly through state_characteristic. Existing template sensors to access individual characteristics can be removed. In case you are interested in multiple characteristics, you need to define multiple statistics sensors.

Many characteristics were renamed and additional ones were added, including a few for binary source sensors. Consider opening a feature request if your use case is not directly covered.

(@ThomDietrich - #59867) (statistics docs)

Templates: timestamp_local and timestamp_utc

The timestamp_local and timestamp_utc template functions/filters have changed their output format. The timestamp is now formatted to iso standards and contains timezone information.

Previously a timestamp from these would look like: 2016-07-21 16:39:04. Now it is formatted as: 2016-07-21T16:39:04+01:00.

This change may break templates that need a specific format, in those cases, you can use the timestamp_custom template filter instead.

(@jbouwh - #60269)

Trafikverket Weather Station

The Trafikverket Weather Station integration migrated to configuration via the UI. Configuring Trafikverket Weather Station 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.

(@gjohansson-ST - #60078) (trafikverket_weatherstation docs)

Twente Milieu

Due to the modernization of the Twente Milieu integration; the twentemilieu.update service has been removed.

You can now use the homeassistant.update_entity service with the Twente Milieu integration as a replacement for the removed service.

(@frenck - #59632) (twentemilieu docs)

Velbus

The previously deprecated YAML configuration of the RVelbus integration has been removed.

Velbus 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.

(@Cereal2nd - #60411) (velbus docs)

Viessmann ViCare

The Viessmann ViCare integration migrated to configuration via the UI. Configuring Viessmann ViCare 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.

(@oischinger - #56691) (vicare docs)

WLED

The led_count and max_power attributes have been removed from the sensor entity that provides the estimated current of the WLED device. These have been replaced by their own sensor entities.

If you have been using the attributes in your automation or scripts, you'll need to adjust those to reflect these changes.

(@frenck - #58839) (wled docs)

---

The speed, palette name, intensity, and reverse effect indicator attributes have been removed from the WLED light entities. They all have been replaced by their own, dedicated, number and switch entities.

If you rely on these attributes in your automations or scripts, you'll need to adjust those to this change.

(@frenck - #60535) (wled docs)

---

The wled.effect and wled.preset services have been removed. For both services, full replacements are available as normal entities in Home Assistant.

If you are still using these services in your automation or script, please replace them with service calls to their native entities instead.

(@frenck - #60537) (wled docs)

Yamaha MusicCast

Only one Home Assistant device was created for a Yamaha MusicCast device, and the media player entities of all zones were part of this device.

As of this release, every zone media player will be located in its own Home Assistant device. For single zone devices, nothing will change and all your automations, scripts, scenes, etc., should work in the same way as before.

A new device will be created for multi-zone devices for every non-main zone (e.g., zone2 or zone3). The media_player of the main-zone will remain in the original device with all its properties, scripts, automations and scenes, configured for it.

For other zones, you will have to set the area of the newly generated devices for the various zones manually. If you created scripts, automations, or scenes with the device as a target and want them to work for non-main zones, you will have to add the newly added devices as a target to your script/automation/scene.

If you used the media player entity as a target, everything should still work like before.

(@micha91 - #58285) (yamaha_musiccast docs)

Z-Wave JS

Some entities have been marked as configuration entities, e.g., default tone of siren devices and protection mode of smart plugs.

Configuration entities:

• Are not included in a service call targeting a whole device or area.
• Are, by default, not exposed to Google Assistant or Alexa.
• Are shown on a separate card on the device configuration page.
• Do not show up on the automatically generated Lovelace Dashboards.

(@MartinHjelmare - #59157 #58703 #59474) (zwave_js docs)

Farewell to the following

The following integrations are no longer available as of this release:

• Dyson has been removed. The integration has been broken for a long time now, so its time for it to go, (@epenet - #59401)
• IOTA has been removed. The protocol is no longer compatible/usable with this integration. (@lambtho12 - #59380
• Loop Energy has been removed. Loop has shutdown their API in November 2020. (@cgarwood- #61175)
• myChevrolet has been removed. It has been broken for 6 months and GM keeps actively hardening their authentication; preventing the integration to work. (@sdague - #59629)

Energy Dashboard

The configuration of the Energy Dashboard has moved.

Previously this was found as a menu item in the configuration screen, but has now been moved into the "Dashboard" menu item.

This keeps the configuration of all dashboards in a single place.

(@zsarnett - #11386)

Python 3.8 support dropped

Python 3.8 support has previously been deprecated and now has been removed. Home Assistant now requires Python 3.9 to run.

If you are using Home Assistant OS, Home Assistant Container, or Home Assistant Supervised installation method, you don't have to do anything. In those cases, we handle this all for you. Your system has been using Python 3.9 for quite some time already.

(@frenck - #63883)

GPIO Integrations

As of this release, all integrations interfacing with GPIO directly, have been deprecated.

There are multiple reasons for this, which includes a general low usage of these integrations. For most Home Assistant installations, GPIO isn't easily usable and more often the integrations are unmaintained.

More information can be found in Architectural Decision Record 0019.

Additionally, there are many projects around that handle these purposes of GPIO better than Home Assistant. For example, our sister project ESPHome, or the MQTT IO project, and many more.

We do not forbid the use of GPIO, but we are merely deprecating and removing built-in integrations, providing GPIO functionality from Core. We welcome custom integrations (existing or new ones) to provide alternatives. However, for most cases we recommend on using dedicated hardware, like an ESP device, instead.

The following integrations have been deprecated and will be removed in Home Assistant Core 2022.4:

• BeagleBone Black GPIO
• BH1750
• Blinkt!
• Bosch BME280 Environmental Sensor
• Bosch BME680 Environmental Sensor
• Bosch BMP280 Environmental Sensor
• DHT Sensor
• Enviro pHAT
• HTU21D(F) Sensor
• mcp23017
• MH-Z19 CO2 Sensor
• Orange Pi GPIO
• pcal9535a
• pi4ioe5v9xxxx
• PiFace Digital I/O (PFIO)
• Piglow
• pigpio Daemon PWM LED
• Raspberry Pi RF
• Rasphihats
• Sense HAT
• Sensirion SHT31
• Time of Flight

The following integration have been deprecated and will be removed in Home Assistant Core 2022.6:

• 1-Wire (SysBus only!)
• Raspberry Pi GPIO

Note: 1-Wire is a special case, as it supports both the SysBus and connecting to a remote owfs server. The use of the SysBus is deprecated, however, connecting to a remote owfs server is not.

Update: We've been notified by a developer that the Raspberry Pi GPIO integration will be made available via HACS.

Binary Sensors

Previously, binary_sensor entities could have the state on, off, and in case the device was unreachable: unavailable.

However, compared to other entities, it wasn't able to have the unknown state, which has been added this release.

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 take this new unknown state into account.

(@frenck - #60193) (binary_sensor docs)

Groups: Locks

The behavior of grouped locks has been reversed such that "unlocked" is mapped to on and "locked" to off.

This means that:

• A group with mixed domains will be considered on if any lock included in the group is unlocked.
• A group of locks will be considered "unlocked" if any lock included in the
• group is unlocked.

(@emontnemery - #62580) (lock docs) (group docs)

Fan/Humidifer/Light/Remote/Siren/Switch/Vacuum

Previously, toggle-based entities (like fan, light, switch, remote, siren, vacuum, humidifier) could have the state on or off, and in case the device was unreachable: unavailable. However, compared to other entities, toggle entities weren't able to have an unknown state, this now has changed.

As of now, toggle-based entities can have the on, off, unavailable, or unknown state.

You might need to adapt your automations or scripts to take this new unknown state into account.

(@frenck - #64621)

Command-line arguments and OS check

Home Assistant no longer supports managing a PID file or creation of a daemon process. Users who use a customized core or container installation may need to update their startup scripts.

The --runner option is no longer supported by the hass command. Requesting a restart from the UI will now always exit with exit code 100. You will need to update your startup scripts to handle the restart, like our Systemd service example.

Home Assistant will exit immediately if not started from a supported operating system according to ADR-0016: Linux (including WSL) or OSX. A new command line parameter --ignore-os-check has been added to allow overriding this check.

(@emontnemery - #64345) #64347) #64352)

Advantage Air

The advantage_air.set_myzone service has been deprecated and will be removed in a future version of Home Assistant.

Please use the select.select_option service on the MyZone select entity to change this value on supported systems instead.

(@Bre77 - #58777) (advantage_air docs)

Android TV

The Android TV integration migrated to configuration via the UI. Configuring Android TV 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.

• Add config_flow to AndroidTV integration (@ollo69 - #54444) (androidtv docs) (breaking-change)

API

The /api/discovery_info endpoint was deprecated in 2021.10, and has since only returned blank values. From this version, the /api/discovery_info endpoint has been removed completely.

(@ludeeus - #64534) (api docs)

Apple iCloud

The Apple iCloud integration migrated to configuration via the UI in a previous release already. Configuring Apple iCloud via YAML configuration has now been deprecated and will be removed in a future Home Assistant release.

Your existing YAML configuration is already automatically imported; and thus can be safely removed from your YAML configuration.

(@epenet - #63875) (icloud docs)

Apple Push Notification Service (APNS)

The Apple Push Notification Service (APNS) integration has been deprecated and will be removed in Home Assistant 2022.4. Please note, this does not affect our mobile companion apps; as they do not use this integration for their notifications.

(@frenck - #64629) (apns docs)

Aurora ABB PowerOne Solar PV

The previously deprecated YAML configuration of the Aurora ABB PowerOne Solar PV integration has been removed.

Aurora ABB PowerOne Solar PV 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.

(@tkdrob - #62317) (aurora_abb_powerone docs)

AVM FRITZ!Box Tools

The previously deprecated YAML configuration of the AVM FRITZ!Box Tools integration has been removed.

AVM FRITZ!Box Tools 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.

@epenet - #63857) (fritz docs)

---

The reboot and reconnect services are deprecated and will be removed in future release. Please use the newly provided button entities instead.

(@chemelli74 - #61483) (fritz docs)

AVM FRITZ!SmartHome

The lock and devicelock attributes are removed from all entities and now exposed as own sensors.

(@mib1185 - #60426) (fritzbox docs)

Azure Event Hub

The Azure Event Hub integration migrated to configuration via the UI. Configuring Azure Event Hub 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.

(@eavanvalkenburg - #61155) (azure_event_hub docs)

BMW Connected Drive

The charging_time_remaining (in hours) has been replaced with charging_end_time (timestamp) to not clutter the Home Assistant state machine.

You might need to adapt your automations or scripts for this change.

(@rikroe - #60942) (bmw_connected_drive docs)

---

All ``bmw_connected_drive.*services are deprecated. Please use the new button entities with thebutton.press` service instead.

(@rikroe - #63136) (bmw_connected_drive docs)

Bond

The custom start_increasing_brightness, start_decreasing_brightness and stop services are now deprecated and will be removed in a future release.

Please use the new button entities, that replace those, instead.

(@bdraco - #64725) (bond docs)

Broadlink

The previously deprecated YAML configuration of the Broadlink integration has been removed.

Broadlink 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.

(@tkdrob - #62341) (broadlink docs)

CO2 Signal

The previously deprecated YAML configuration of the CO2 Signal integration has been removed.

CO2 Signal 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.

(@tkdrob - #62343) (co2signal docs)

CPU Speed

The CPU Speed integration migrated to configuration via the UI. Configuring CPU Speed 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.

(@frenck - #62929) (cpuspeed docs)

DLNA Digital Media Renderer

The previously deprecated YAML configuration of the DLNA Digital Media Renderer integration has been removed.

DLNA Digital Media Renderer 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.

(@tkdrob - #62344) (dlna_dmr docs)

DNS IP

The DNS IP integration migrated to configuration via the UI. Configuring DNS IP 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.

(@gjohansson-ST - #62843) (dnsip docs)

DoorBird

The relays and IR light switches are removed and replaced with corresponding buttons entities. Any scripts or automations which reference these switches to turn them on should change to instead press the button instead.

(@flacjacket - #63995) (doorbird docs)

DSMR

The sensor.energy_consumption_total sensor for DSMR versions 2.2 and 4 has been removed. Meters with these versions do not provide this data, so this sensor can be safely removed. You might need to clean up the orphaned entity in your setup.

(@rhpijnacker - #63436) (dsmr docs)

Efergy

The previously deprecated YAML configuration of the Efergy integration has been removed.

Efergy 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.

(@tkdrob - #61520) (efergy docs)

Enphase Envoy

The previously deprecated YAML configuration of the Enphase Envoy integration has been removed.

Enphase Envoy 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.

(@tkdrob - #61840) (enphase_envoy docs)

Environment Canada

The previously deprecated YAML configuration of the Environment Canada integration has been removed.

Environment Canada 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.

(@tkdrob - #61839) (environment_canada docs)

---

The sensors no longer have Timestamp as an extra state attribute, instead, use the new timestamp sensor that can be used in automations that track state changes.

The alert sensors (advisories, endings, statements, warnings, and watches) state is now a count of the number of active alerts for the sensor type and the extra state attributes contain the alert text and alert timestamp.

The attributes are named alert_<x> and alert_time_<x> where <x> is 1 for alert 1, 2 for alert 2, etc.

(@gwww - #58615) (environment_canada docs)

Fan

This is more a breaking change for custom integration developers.

Now that all core fans are using the new fan entity model, the compatibility shim has been removed. Custom integrations that have not yet switched to the new fan model may be affected. For more information see:

https://developers.home-assistant.io/docs/core/entity/fan/#deprecated-properties

Preset modes and percentages will continue to be translated back to legacy speeds until 2022.3 in order to give users a bit more time to update automations.

(@bdraco - #59781) (fan docs)

Fibaro

The energy values are exposed now as separate sensor entities and therefore the state attribute current_energy_kwh was removed from all other entities.

If you use the state attribute current_energy_kwh you need to change that to use the new energy sensors instead.

(@rappenze - #63697) (fibaro docs)

Flume

The previously deprecated YAML configuration of the Flume integration has been removed.

Flume 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.

(@tkdrob - #61517) (flume docs)

FortiOS

The integration now requires FortiOS 6.4.3 and newer.

(@kimfrellsen - #61970) (fortios docs)

Foscam

The previously deprecated YAML configuration of the Foscam integration has been removed.

Foscam 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.

(@tkdrob - #61761) (foscam docs)

Foursquare

The data associated with foursquare.checkin event is now available as a dictionary item with key "text".

If you use this event in your automation or scripts, you'd need to adjust to match this change.

(@epenet - #63982) (foursquare docs)

GitHub

The YAML configuration for the github sensor platform has been removed.

There was no viable automatic migration of the configuration, so you need to manually remove the configuration from your configuration file and set it up again in the integration panel.

Previously this integration created 1 sensor for each repository, now this is split out to multiple entities which are mostly disabled by default (you can enable the entities you want this integration to provide).

Support for GitHub enterprise has been removed.

(@ludeeus - #64190) (github docs)

Google Maps Travel Time

The previously deprecated YAML configuration of the Google Maps Travel Time integration has been removed.

Google Maps Travel Time 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.

(@tkdrob - #62468) (google_travel_time docs)

HomeKit

HomeKit will now automatically exclude entities with an entity category such as a configuration or diagnostic entity unless they have been explicitly included.

To explicitly include an entity:

• YAML: Add the entity to the filter in either the include_entities or include_entity_globs fields.
• UI: Select the entity in the UI in include mode. If you are using exclude mode, a second bridge can be created in include mode.

(@bdraco - #64492) (homekit docs)

Honeywell Total Connect Comfort (US)

The previously deprecated YAML configuration of the Honeywell Total Connect Comfort integration has been removed.

Honeywell Total Connect Comfort 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.

(@tkdrob - #62469) (honeywell docs)

iOS

The Home Assistant iOS/macOS app supports notification actions defined in the notification itself; the old method of defining push categories in the iOS integration is now deprecated and will be removed in 2022.4.

(@zacwest - #61078) (ios docs)

Keenetic NDMS2 Router

The previously deprecated YAML configuration of the Keenetic NDMS2 Router integration has been removed.

Keenetic NDMS2 Router 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.

(@epenet - #63860) (keenetic_ndms2 docs)

Launch Library

The Launch Library integration migrated to configuration via the UI. Configuring Launch Library 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 - #62416) (launch_library docs)

---

Attributes on the current sensor is changed. Names of these attributes are changed to better describe what information they provide. (Ex. agency changed name to provider as this is the more correct terminology.) New attributes are added to give more information about where it takes place.

The stream attribute ios moved to the new sensor, and changed its name to stream_live as it represents if the stream is live and not if a stream is available.

And finally, the attribute launch_time moved into its own sensor. This made it possible to add some information about the launch window start and end as attributes for the new sensor. This sensor will also contain the stream_live attribute.

(@DurgNomis-drol - #64203) (launch_library docs)

LG webOS Smart TV

The LG webOS Smart TV integration migrated to configuration via the UI. Configuring LG webOS Smart TV 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.

The turn on action for turning on the TV via WakeOnLan or HDMI-CEC was using a service call via YAML, and the turn on action is changed to use a custom automation trigger webostv.turn_on or a device trigger automation that can be setup from the UI.

Example trigger automation:

automation:
  trigger:
    - platform: webostv.turn_on
      entity_id: media_player.lg_webos_smart_tv
  action:
    - service: wake_on_lan.send_magic_packet
      data:
        mac: AA-BB-CC-DD-EE-FF

(@thecode - #64117) (webostv docs)

Logitech Squeezebox

The previously deprecated YAML configuration of the Logitech Squeezebox integration has been removed.

Logitech Squeezebox 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.

(@tkdrob - #62537) (squeezebox docs)

Magic Home

The previously deprecated YAML configuration of the Magic Home integration has been removed.

Magic Home 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.

(@tkdrob - #61844) (flux_led docs)

Media Player Classic Home Cinema (MPC-HC)

The Media Player Classic Home Cinema (MPC-HC) integration has been deprecated and will be removed in Home Assistant Core 2022.4.

This integration is removed under Architectural Decision Record 0004.

(@frenck - #63598) (mpchc docs)

MQTT

The MQTT lights no longer support, the previously deprecated, value_template;state_value_template should be used instead.

(@emontnemery - #62682) (mqtt docs)

---

Previouysly MQTT climate would only publish to hold_command_topic or away_mode_command_topic if the new mode is not the same as the current state.

As of this release MQTT always publishes on both command topics (hold_command_topic and away_mode_command_topic) (if defined) which makes it more predictable what update the MQTT device will receive.

(@jbouwh - #63463) (mqtt docs)

---

The send_if_off config parameter of the climate platform, which limits publishing if the current operation mode is HVAC_MODE_OFF, is now deprecated.

This will break applications that depend on this feature.

(@jbouwh - #63814) (mqtt docs)

Nanoleaf

The Nanoleaf integration migrated to configuration via the UI in a previous release already. Configuring Nanoleaf via YAML configuration has now been deprecated and will be removed in a future Home Assistant release.

Your existing YAML configuration is already automatically imported; and thus can be safely removed from your YAML configuration.

(@milanmeu - #63404) (nanoleaf docs)

Nest

The Legacy "Works With Nest API" is deprecated and support will be removed in Home Assistant Core 2022.5; See our documentation for using the Smart Device Management API instead.

Read why and about potential alternatives.

(@allenporter - #63027) (nest docs)

NETGEAR

The previously deprecated YAML configuration of the NETGEAR integration has been removed.

NETGEAR 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.

(@epenet - #63862) (netgear docs)

Nissan Leaf

The service to start a charge has been deprecated; it is replaced with a button.

Replace the nissan_leaf.start_charge service in any existing automations with button.press for the new button.start_NICKNAME_charging entity.

The nissan_leaf.start_charge service is now deprecated and will be removed in a future release.

(@filcole - #62948) (nissan_leaf docs)

Nmap Tracker

The previously deprecated YAML configuration of the Nmap Tracker integration has been removed.

Nmap Tracker 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.

(@epenet - #63863) (nmap_tracker docs)

Nuki

The previously deprecated YAML configuration of the Nuki integration has been removed.

Nuki 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.

(@tkdrob - #62470) (nuki docs)

OpenGarage

The previously deprecated YAML configuration of the OpenGarage integration has been removed.

OpenGarage 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.

• Remove deprecated yaml config from opengarage (@tkdrob - #61961) (opengarage docs) (breaking-change)

Philips TV

The previously deprecated YAML configuration of the Philips TV integration has been removed.

Philips TV 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.

(@tkdrob - #62471) (philips_js docs)

PVOutput

The PVOutput integration migrated to configuration via the UI. Configuring PVOutput 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.

Additionally, all sensor attributes of the PVOutput sensor, have been extracted in their own dedicated sensors.

This applies to the following PVOutput attributes:

• energy_generation
• power_generation
• energy_consumption
• power_consumption
• efficiency
• temperature
• voltage

If you relied on these in your automation or scripts, you need to adapt those to use the new separate sensors instead. The attributes are currently available, however, deprecated and will be removed in Home Assistant Core 2022.4.

(@frenck - #62667 #62894) (pvoutput docs)

ReCollect Waste

ReCollect Waste no longer stories "next pickup" information as attributes of the "current pickup" sensor; instead, both pickups are now their own sensors.

(@bachya - #62558) (recollect_waste docs)

RIVM Stookalert

The previously deprecated YAML configuration of the Stookalert integration has been removed.

Stookalert 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.

(@frenck - #61007) (stookalert docs)

Samsung SyncThru Printer

The previously deprecated YAML configuration of the Samsung SyncThru Printer integration has been removed.

Samsung SyncThru Printer 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.

(@tkdrob - #62541) (syncthru docs)

Sensibo

The Sensibo integration migrated to configuration via the UI. Configuring Sensibo 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.

(@gjohansson-ST - #60900) (sensibo docs)

Sensor.Community (previously: Luftdaten)

The Luftdaten integration has been renamed to Sensor.Community; which is the new name of the Luftdaten project.

The previously deprecated YAML configuration of this integration has been removed.

Sensor.Community 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.

(@frenck - #61748 #62865) (luftdaten docs)

SMA Solar

The previously deprecated YAML configuration of the SMA Solar integration has been removed.

SMA Solar 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.

(@tkdrob - #62472) (sma docs)

SolaX Power

The SolaX Power integration migrated to configuration via the UI. Configuring SolaX Power 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.

(@tokenize47 - #56620) (solax docs)

SwitchBot

The SwitchBot integration migrated to configuration via the UI in a previous release already. Configuring SwitchBot via YAML configuration has now been deprecated and will be removed in a future Home Assistant release.

Your existing YAML configuration is already automatically imported; and thus can be safely removed from your YAML configuration.

(@tkdrob - #62583) (switchbot docs)

Synology DSM

The reboot and shutdown services are deprecated and will be removed in a future release. Please use the new button entities instead.

(@mib1185 - #57352) (synology_dsm docs) (breaking-change)

Templates: Binary Sensors

Template trigger binary sensor should start with unknown value rather than always starting with false/off. This matches the template binary sensor behavior with other sensors.

(@amosyuen - #62769) (template docs)

TP-Link Kasa Smart

The previously deprecated YAML configuration of the TP-Link Kasa Smart integration has been removed.

TP-Link Kasa Smart 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.

(@bdraco - #62457) (tplink docs)

Trafikverket Train

The planned time, estimated time and actual time sensor attributes have been corrected to be UTC isoformatted strings which is standard in Home Assistant.

Previously displayed as 2021-12-23T09:07:00 and now correctly set as 2021-12-23T09:07:00+00:00.

This may affect templates or automations based on these attributes.

(@gjohansson-ST - #62636) (trafikverket_train docs)

Twinkly

Key host is removed from the (extra) state attribute of the light entity.

(@RobBie1221 - #64139) (twinkly docs)

Vallox

The Vallox integration migrated to configuration via the UI. Configuring Vallox 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.

(@slovdahl - #62780) (vallox docs)

Version

The Version integration migrated to configuration via the UI. Configuring Version 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.

Additionally, the source and channel attributes have been removed from the Version sensor for the local source.

(@ludeeus - #54642 #64827) (version docs)

VeSync

Previous versions of this integration exposed power and energy usage from VeSync outlets as state attributes on the switch entity itself. This used the deprecated properties: current_power_w and today_energy_kwh.

In this version, these two attributes have been removed from the switch entity and split into two new diagnostic sensor entities that are attached to the same Device.

Automations and template entities based on the state attribute mechanism should be updated accordingly.

(@decompil3d - #61837) (vesync docs)

Viessmann ViCare

The scan interval option has been removed, since the default should be fine in almost all cases.

If you really need more fine-grained control you can disable automatic updates in the system settings for the Viessmann ViCare integration and automate the polling of the entities with the homeassistant.update_entity service.

(@oischinger - #63343) (vicare docs)

VIZIO SmartCast

If an integrated vizio TV supports apps and the source is currently a non-app input (e.g. HDMI-1), the app_id and app_name attributes will no longer be in the media player entity's state.

When the TV is using an app, the app_name will still always be visible and the app_id will continue to only be shown if the app is not recognized.

(@raman325 - #64025) (vizio docs)

VLC media player Telnet

The previously deprecated YAML configuration of the VLC media player Telnet integration has been removed.

VLC media player Telnet 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.

(@tkdrob - #62542) (vlc_telnet docs)

Waze Travel Time

The previously deprecated YAML configuration of the Waze Travel Time integration has been removed.

Waze Travel Time 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.

(@tkdrob - #62543) (waze_travel_time docs)

WebSocket API / Media Source

This concerns custom integration developers only.

The parameters for async_sign_path have changed. Refresh token is now a keyword parameter. If called as part of a HTTP or WebSocket request, the users refresh token will automatically be used.

(@balloob - #64337)

Whois

The Whois integration migrated to configuration via the UI. Configuring Whois 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.

(@frenck - #63069) (whois docs)

Z-Wave JS

Due to a schema change, zwave-js-server version 1.14.0 or greater is required. Ensure you are using the latest version of zwave-js-server (or the add-ons that provide those).

(@raman325 - #64407) (zwave_js docs)

Zero-configuration networking (zeroconf)

This change is only a concern for custom integration developers.

Currently zeroconf matching only allows matching the macaddress, model, and manufacturer properties along with the name from the ZeroconfServiceInfo.

Since properties are arbitrarily defined by the zeroconf service, the list of named properties has grown over time.

Matching now allows for any arbitrarily defined property. All property matches must be lowercase, wildcards are supported

The top level keys model, manufacturer, and macaddress are now deprecated from the manifest.json file and should be moved into a properties dict.

For example:

-    {"type":"_airplay._tcp.local.","model":"appletv*"}
+    {"type":"_airplay._tcp.local.","properties":{"model":"appletv*"}}

(@bdraco - #62133) (zeroconf docs)

Farewell to the following

The following integrations are no longer available as of this release:

• TaHoma has been removed. The integration has been broken and now been superseded by the Overkiz integration. (@iMicknl - #62607)
• Arduino the now long time deprecated integration has been removed. (@frenck - #63406)
• EE Bright Box has been broken and disabled for over a year now. It has now been removed. (@epenet - #63839)

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.

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)

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)

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)

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)

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)

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)

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.

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

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

Configuring those options can instead be done via the UI.

(@emontnemery - #66247) (documentation)

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)

NINA

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

(@DeerMaximum - #65914) (documentation)

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)

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)

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)

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)

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)

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)

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.

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

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)

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)

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)

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)

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.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)

Vallox

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)

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 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

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.

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.

(@frenck - #59729)

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)

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)

Service Calls

If an entity is explicitly referenced as a target for a service that the entity doesn't support, we now raise an error instead of silently ignoring it.

This helps detect automations or scripts that used to silently fail.

(@balloob - #68394)

Switches - Energy attributes

In the August 2021 release, we deprecated all energy-related attributes from switches. The attributes are: current_power_w and today_energy_kwh. Those attributes should have been separate power and energy sensors instead.

All integrations affected were notified on July 22, 2021, of requiring a change.

As of this release, the attributes have been removed from the switch core entity platform, meaning the current_power_w and today_energy_kwh attributes are no longer available for the following:

• ATEN Rack PDU
• Belkin WeMo
• D-Link Wi-Fi Smart Plugs
• Edimax
• ELV PCA
• Emulated Kasa
• Fibaro
• Hive
• HomematicIP Cloud
• MQTT
• myStrom
• Netio
• Ubiquiti mFi mPort
• Vera

(@balloob - #68821)

Android TV

The previously deprecated YAML configuration of the Android TV integration has been removed.

Android TV 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.

(@tkdrob - #68339) (documentation)

Apple iCloud

The previously deprecated YAML configuration of the Apple iCloud integration has been removed.

Apple iCloud 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.

(@balloob - #69006) (documentation)

Awair

The previously deprecated YAML configuration of the Awair integration has been removed.

Awair 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.

(@tkdrob - #68572) (documentation)

BMW Connected Drive

The previously deprecated YAML configuration of the BMW Connected Drive integration has been removed.

BMW Connected Drive 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.

(@rikroe - #66965) (documentation)

Brunt

The previously deprecated YAML configuration of the Brunt integration has been removed.

Brunt 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.

(@balloob - #69024) (documentation)

Climacell / Tomorrow.io

ClimaCell as a company rebranded to Tomorrow.io and as such we will be deprecating the climacell integration in favor of the new tomorrowio integration.

For any climacell users using a v4 API key, the migration from the old integration to the new one will happen automatically. If you are a climacell user using a v3 API key, you will need to sign up for a v4 API key to complete the migration, but once you have provided the new key, your configuration (or configurations) will be migrated over automatically.

For now, v3 users will still have access to their existing ClimaCell configurations before they submit the new API key so that your automations and dashboards still work.

In a future release, we will be removing most of the code from the climacell integration so that the migrations will still happen, but the original integration will no longer work.

(@raman325 - #68156) (documentation)

CPU Speed

The previously deprecated YAML configuration of the CPU Speed integration has been removed.

CPU Speed 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.

(@frenck - #67166) (documentation)

Deluge

The Deluge integration migrated to configuration via the UI. Configuring Deluge 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 - [#58789]) (documentation)

Discord

The Discord integration migrated to configuration via the UI. Configuring Discord 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 - #61069) (documentation)

DNS IP

The previously deprecated YAML configuration of the DNS IP integration has been removed.

DNS IP 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.

(@balloob - #69007) (documentation)

Dune HD

The Dune HD integration has previously migrated to configuration via the UI. Configuring Dune HD 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 thus can be safely removed from your YAML configuration.

(@tkdrob - #68381) (documentation)

Eight Sleep

The partner parameter was deprecated in 2021, but it was still accepted in your configuration. The partner option has now been removed; please remove the partner parameter from your YAML configuration before updating.

(@raman325 - #68381) (documentation)

Enphase Envoy

The last_reported attribute for Enphase Envoy inverters is now a separate timestamp sensor.

Each last reported sensor is disabled by default since it generates a significant amount of state changes and database rows. Each last reported sensor can be enabled in the UI.

(@bdraco - #68360) (documentation)

EZVIZ

The previously deprecated YAML configuration of the EZVIZ integration has been removed.

EZVIZ 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.

(@frenck - #69031) (documentation)

Fibaro

The Fibaro integration migrated to configuration via the UI. Configuring Fibaro 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.

(@rappenze - #65203) (documentation)

File Size

The File Size integration migrated to configuration via the UI. Configuring File Size 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.

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

---

Additional attributes for the File Size sensors has been extracted into their own sensors which are disabled by default.

If you were previously using any of these attributes your automations, scripts etc. need to be updated to use the new sensors.

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

Fronius

The previously deprecated YAML configuration of the Fronius integration has been removed.

Fronius 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.

(@frenck - #69032) (documentation)

• Remove deprecated YAML configuration from Fronius (@frenck - #69032) ([fronius docs]) (breaking-change) (beta fix)

Generic Camera

The Generic Camera integration migrated to configuration via the UI. Configuring Generic Camera 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.

(@davet2001 - #52360) (documentation)

Huawei LTE

The previously deprecated YAML configuration of the Huawei LTE integration has been removed.

Huawei LTE 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.

(@scop - #68728) (documentation)

Launch Library

The previously deprecated YAML configuration of the Launch Library integration has been removed.

Launch Library 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.

(@balloob - #69008) (documentation)

LG webOS Smart TV

The previously deprecated YAML configuration of the LG webOS Smart TV integration has been removed.

LG webOS Smart TV 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.

(@thecode - #69043) (documentation)

Mazda

The Mazda services start_engine, stop_engine, turn_on_hazard_lights, and turn_off_hazard_lights are deprecated and have been replaced by button entities. Please use the button entities instead.

(@bdr99 - #67597) (documentation)

---

The Mazda services start_charging and stop_charging are deprecated and replaced by a charging switch entity. Please use the switch entity instead.

(@bdr99 - #68025) (documentation)

Met.no

The previously deprecated YAML configuration of the Met.no integration has been removed.

Met.no 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.

(@frenck - #69027) (documentation)

Modbus

Setting reverse_order has not been allowed (or worked) for a long time and is removed.

The previously deprecated data_count has been removed.

(@janiversen - #67236) (documentation)

---

The previously deprecated data types int, uint, and float have been removed.

For the devices that use non-standard register size, "count" can be used to overwrite the default count of registers.

(@janiversen - #67268) (documentation)

---

There is now an automatic distinction between calling write_register and write_registers, depending on the configured datatype (more than 16bits uses write_registers).

The special situation, where write_registers, count=1 is no longer supported.

(@janiversen - #67268) (documentation)

MySensors

The MySensors integration migrated to configuration via the UI a year ago. Configuring MySensors via YAML configuration has been deprecated and will be removed in a future Home Assistant release.

Your existing YAML configuration has been automatically imported since a long time; and thus can be safely removed from your YAML configuration.

(@MartinHjelmare - #68504) (documentation)

Nanoleaf

The previously deprecated YAML configuration of the Nanoleaf integration has been removed.

Nanoleaf 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.

(@balloob - #69004) (documentation)

Nest

Legacy Works with Nest API deprecation is put on hold until issues with SDM API OAuth signups are resolved (so this is an un-breaking change).

(@allenporter - #68715) (documentation)

Pi-hole

The binary sensor entities that would show if an update is available for the Core, Web, or FTL component has been deprecated and will be removed in Home Assistant Core 2022.6.

The PI-Hole integration now provides update entities to replace the deprecated entities.

(@mib1185 - #68749) (documentation)

Plex Media Server

Support for multiple Plex Media Servers in the media browser has been added.

Automations and scripts which used the media picker to add Plex media items may need to be updated if more than one Plex integration/server is configured.

(@jjlawren - #68321) (documentation)

Plugwise

The climate entity attributes selected_schema and available_schemas will be removed in a future release.

This release introduces the select platform featuring these attribute values as well as the ability to switch a schedule.

(@CoMPaTech - #68303) (documentation)

---

The naming of the locally present outdoor temperature sensor connected to OpenTherm devices has been improved: outdoor_air_temperature.

E.g. former sensor.opentherm_outdoor_temperature is now visible as sensor.opentherm_outdoor_air_temperature.

The use of the zipcode-based outdoor_temperature for other devices has not changed.

(@CoMPaTech - #68303) (documentation)

PVOutput

The previously deprecated YAML configuration of the PVOutput integration has been removed.

PVOutput 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.

(@frenck - #67162) (documentation)

---

All, previously deprecated, additional sensor attributes of the PVOutput sensor, have now been removed. All of these attributes now have their own dedicated sensor.

This applies to the following PVOutput attributes:

• energy_generation
• power_generation
• energy_consumption
• power_consumption
• efficiency
• temperature
• voltage

If you relied on these in your automations or scripts, you need to adopt those to use the new separate sensors instead.

(@bdraco - #68481) (documentation)

Recorder

The following breaking changes are only breaking if you consume the Home Assistant Core database manually or in custom integrations; For example, when using custom queries or doing data analytics on your database.

---

Attributes are now stored in a state_attributes table, storing the same set of attributes once (many to one relationship).

Attributes represent roughly 21% of the database size. (28% if you exclude statistics). On a few of the analyzed production instances, attributes ranged from 82-88% duplicates of another set of attributes. Expected is that this change will reduce the database size by roughly between 13-16% on average.

(@bdraco - #68224) (documentation)

---

The domain column has been removed from the states table. The domain can be derived from the entity_id.

(@bdraco - #68404) (documentation)

---

The attributes for the sun.sun entity are no longer recorded in the database.

As historical data can be derived from the astral library without the need to fetch it from the database, it was decided to remove the sun attributes from the database since it frequently generates new attribute rows in the database.

(@bdraco - #68404) (documentation)

---

Integrations and platforms can now provide hints to the recorder to exclude specific entity state attributes from being recorded.

This excludes attributes that hold little to no historical value or are a static value. This significantly reduces the amount of data stored.

The following attributes are no longer recorded:

• For all entities: attribution and supported_features.
• Camera: token and entity_picture.
• Climate: hvac_modes, fan_modes, swing_modes, min_temp, max_temp, min_humidity, max_humidity, target_temp_step, and preset_modes.
• Fan: preset_modes.
• Light: color_modes, min_mireds, max_mireds, and effect_list.
• Media Player: entity_picture_local, source_list, media_postition, and media_postition_updated_at.
• Water Heater: operation_list, min_temp, and max_temp.
• Humidifier: min_humidity, max_humidity, and available_modes.
• Number: min, max, step, and mode.
• Select: options.
• Siren: available_tones.
• Vacuum: fan_speed_list.
• Weather: forecast.

(@bdraco - #68404 #69155 #69156 #69158 #69159 #69165 #69192 #69193 #69194 #69195 #69196 #69199)

(@frenck - #69205 #69209)

RFXCOM RFXtrx

Support for signal repetition for devices has been removed. RFXCOM internally repeats packets as needed per protocol.

(@elupus - #67675) (documentation)

Sensibo

Sensibo Air devices with an active room sensor (as the main measurement sensor) will now retrieve the temperature and humidity from the room sensor.

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

---

The previously deprecated YAML configuration of the Sensibo integration has been removed.

Sensibo 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.

(@frenck - #69028) (documentation)

SiteSage Emonitor

The avg_power and max_power extra attributes for Emonitor have been removed and now have their own sensors.

(@bdraco - #68479) (documentation)

SleepIQ

The sleep number firmness sensor entity in the SleepIQ integration is deprecated and will be removed in a future release. A number entity is available, providing the same information and can be used instead.

(@mfugate1 - #65841) (documentation)

SoChain

The SoChain integration has been disabled, its functionality relies on older Python packages we can not provide.

(@emontnemery - #68856) (documentation)

Solax

The previously deprecated YAML configuration of the Solax integration has been removed.

Solax 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.

(@balloob - #69003) (documentation)

Sonos

Favorites are no longer included in the "Source" dropdown on Sonos devices. These have been moved to the Media Browser and are also available using the media selector (a.k.a. "Play Media") in automation/script builders.

The selectable "Source" dropdown is now limited to static inputs, such as TV and line-in sources.

The media_player.select_source service call will continue to accept favorite names. This compatibility feature may be removed in a future release, but there are no current plans to do so.

This change was done to minimize writes to the database. Each modification to the favorites would rewrite the complete list of favorites in the database for each Sonos device.

(@jjlawren - #67931) (documentation)

Supervisor

The binary sensor entities for the Supervisor integration that would show if there was an update available for Home Assistant OS and add-ons have been deprecated and will be removed in Home Assistant 2022.6.

The Supervisor integration now provides update entities to replace the deprecated entities.

(@ludeeus - #68475) (documentation)

SwitchBot

The previously deprecated YAML configuration of the SwitchBot integration has been removed.

SwitchBot 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.

(@balloob - #69002) (documentation)

Synology DSM

The binary sensor entity that would show if there was an update available for the Synology DSM firmware has been deprecated and will be removed in Home Assistant Core 2022.6.

The Synology DSM integration now provides an update entity to replace the deprecated entity.

(@mib1185 - #68664) (documentation)

Tankerkoenig

The Tankerkoenig integration migrated to configuration via the UI. Configuring Tankerkoenig 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.

(@mib1185 - #68386) (documentation)

---

The is_open attribute is removed from all entities and now exposed as its own sensor.

If you have automations or scripts relying on this attribute, you will need to adjust them for this change.

(@mib1185 - #68925) (documentation)

Template

Template binary sensors with on or off delay, or trigger-based binary sensors are now initialized to the last state on Home Assistant Core startup, instead of to unknown.

(@emontnemery - #67546 #67546) (documentation)

Tesla Powerwall

The frequency, current, and voltage attributes on powerwall instant meter sensors are now their own entities.

The is_active attribute has been removed as it can already be derived from the reading. As these sensors generated significant state changes, the new sensors are not enabled by default. They can be enabled in the UI.

(@bdraco - #68345) (documentation)

Trafikverket Train

The Trafikverket Train integration migrated to configuration via the UI. Configuring Trafikverket Train 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.

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

Trafikverket Weather Station

The previously deprecated YAML configuration of the Trafikverket Weather Station integration has been removed.

Trafikverket Weather Station 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.

(@tkdrob - #68336) (documentation)

---

• The attribute for measure time is now a proper iso formatted string.
• The attribute for available has been removed and the entity instead sets its state to unavailable when not available.

Any automation or script depending on these attributes has to be updated to reflect these changes.

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

UniFi Protect

The Unifi Protect last tripped attributes are now their own timestamp sensors. The sensors are not enabled by default to minimize the amount of data stored in the state machine and database. The new sensors can be enabled in the UI.

(@bdraco - #68347) (documentation)

---

The UniFi Protect Privacy Mode switch is now marked as a configuration entity. This means that these switches are no longer automatically exposed or shown on autogenerated Lovelace dashboards, Google Assistant, Alexa, or HomeKit.

(@balloob - #68954) (documentation)

UptimeRobot

This integration now provides a switch entity that will let you pause/resume monitoring of a monitor.

Because of that, you need to use the 'main' UptimeRobot API key; if you previously used that, you will not have to do anything, but if you used the read-only API or a monitor-specific API key, the integration will ask you to reauthorize on the first startup.

To get your API key, go to My Settings on the UptimeRobot website, at the bottom, you will find your key.

(@chemelli74 - #68224) (documentation)

Utility Meter

The utility_meter tariff selector entities are now standard select entities with entity_id select.X instead of custom entities with entity_id utility_meter.X.

In addition:

• The service call utility_meter.select_tariff with argument tariff is deprecated in favor of service call select.select_option with argument option.
• The service call utility_meter.next_tariff is deprecated with no replacement.

Backwards compatibility until the Home Assistant Core release 2022.7:

• The deprecated utility_meter.X entities are still available.
• The service call utility_meter.select_tariff still works on utility_meter.X enties, but a warning is logged when it's called.
• The service call utility_meter.next_tariff still works on utility_meter.X enties, but a warning is logged when it's called.

In Home Assistant Core release 2022.7:

• The deprecated utility_meter.X entities will no longer be available.
• The service call utility_meter.select_tariff will be removed.
• The service call utility_meter.next_tariff will be removed.

(@dgomes - #55690) (documentation)

Version

The previously deprecated YAML configuration of the Version integration has been removed.

Version 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.

(@balloob - #69010) (documentation)

Whois

The previously deprecated YAML configuration of the Whois integration has been removed.

Whois 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.

(@frenck - #67163) (documentation)

WLED

The firmware update binary_sensor and button entities are deprecated and will be removed in Home Assistant 2022.6.

Instead, the WLED integration now provides a brand new update entity that replaces the functionality provided by those entities (and offers more functionality).

(@frenck - #68454) (documentation)

Yale Smart Alarm

The previously deprecated YAML configuration of the Yale Smart Alarm integration has been removed.

Yale Smart Alarm 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.

(@frenck - #69025) (documentation)

Yamaha Music Cast

The previously deprecated YAML configuration of the Yamaha Music Cast integration has been removed.

Yamaha Music Cast 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.

(@frenck - #69033) (documentation)

Z-Wave JS

The Z-Wave JS siren entities will now return unknown as a state if the corresponding driver value is missing.

Previously the state defaulted to off in these cases. You might need to consider this in automations and scripts that rely on a Z-Wave JS siren entity state.

(@MartinHjelmare - #67172) (documentation)

---

The selected fan speed has changed at specific percentages for Inovelli LZW36 fan controllers. Setting the percentage to 1% will no longer enable the 'breeze' mode; that functionality is instead accessed through a preset.

(@mkowalchuk - #60947) (documentation)

Farewell to the following

The following GPIO Integrations have been previously deprecated and have now been removed.

• BeagleBone Black GPIO
• BH1750
• Blinkt!
• BMP280 Environmental Sensor
• Bosch BME280 Environmental Sensor
• Bosch BME680 Environmental Sensor
• DHT Sensor
• Enviro pHAT
• HTU21D(F) Sensor
• MCP23017 I/O Expander
• MH-Z19 CO2 Sensor
• Orange Pi GPIO
• PCAL9535A I/O Expander
• pi4ioe5v9xxxx IO Expander
• PiFace Digital I/O (PFIO)
• Piglow
• pigpio Daemon PWM LED
• Raspberry Pi RF
• Raspihats
• Sense HAT
• Sensirion SHT31
• Time of Flight

More information about the removal of GPIO integrations can be found in Architectural Decision Record 0019.

The following integrations are also no longer available as of this release:

• Apple Push Notification Service (APNS) has been removed. This does not affect our mobile apps! (@frenck - #67158)
• Media Player Classic Home Cinema (MPC-HC), the integration is using web scraping, which is no longer allowed. (@frenck - #67189)
• OpenZWave, was previously deprecated and is now removed. Please use Z-Wave JS instead. (@frenck - #68054)
• SmartHab has been removed. The company behind it has been shut down. (@outadoc - #67874)
• Z-Wave (the old zwave integration), was previously deprecated and is now removed. Please use Z-Wave JS instead. (@frenck - #67221)

Configuration Menu

This release contains several changes to the configuration menu. These are the most important changes.

• The Configuration menu has been renamed to Settings.
• Helpers moved to Devices & services.
• Blueprints moved to Automations & Scenes.
• Areas is now grouped with `Zones.
• Dashboard Resources moved to overflow menu*.
• A brand new System menu housing all system-related settings:

• The Restart button is available in the System menu.
• New Updates menu, which also now provides the ability to join or leave the beta channel from the overflow menu*.
• All logs moved to Logs (Supervisor, audio, etc).
• Backups moved from the Supervisor/Main menu to here.
• Network now has all network related settings previously in the General settings and Supervisor.
• Storage provides information about used space, eMMC Lifetime, and also provides the Move datadisk feature in the overflow menu*.
• Hardware now has the Reboot and Restart Host controls, Available Hardware is available in the overflow menu*.
• System Health moved to its own menu item in the system menu.
• Processor and memory usage was moved into the new System Health menu.
• The integration list with timings, previously shown in the About menu, is moved into the new System Health menu.

Additionally, the developers tools has a brand new YAML tab, which contains the buttons and tools to reload and check your YAML configuration. This was previously known as "Server Controls", but now moved to the developer tools.

* The overflow menu is the menu you see when you click on the three vertical dots in the top right of your screen.

Temperature conversion

Sensors reporting a temperature but not setting device class to temperature will no longer have their values automatically converted. For sensors that are manually configured, users need to set the device class. If the integration providing the sensor does not support setting device class, the sensor's state can be filtered through a template sensor.

(@emontnemery - #69069)

AVM FRITZ!Box Call Monitor

The previously deprecated YAML configuration of the AVM FRITZ!Box Call Monitor integration has been removed.

AVM FRITZ!Box Call Monitor 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.

(@cdce8p - #70829) (documentation)

AVM FRITZ!Box Tools

The binary sensor entity showing that an update is available for the FRITZ!Box firmware has been deprecated and will be removed in Home Assistant 2022.7.

The AVM FRITZ!Box Tools integration now provides an update entity as a replacement.

(@Mask3007 - #70096) (documentation)

BMW Connected Drive

All bmw_connected_drive.* services are removed (deprecated since 2022.2). Please use the new button entities with the button.press service instead.

(@rikroe - #69808) (documentation)

---

The button.<your_vehicle_refresh entity is deprecated and will be removed in a future version. Please use the homeassistant.update_entity service with any BMW entity to force-refresh all platforms from the BMW API.

(@rikroe - #67003) (documentation)

deCONZ

Migrating deCONZ Siren entities from switch platform to siren platform has been removed. This only affects users upgrading from before 2021.10 to 2022.5 or later. At most, this causes lingering unavailable switch entities; which can be manually removed.

(@Kane610 - #70600) (documentation)

---

Migrated deCONZ light entities of type "On/Off Output" to switch from light platform as they are binary devices (only on/off).

(@Kane610 - #70598) (documentation)

Energy

The internal cost and compensation sensor entities, used by the energy dashboard of Home Assistant, are now hidden by default.

(@frenck - #70378) (documentation)

Fibaro

Fibaro lights no longer support deprecated white_value, use rgbw_color instead.

(@rappenze - #69189) (documentation)

Flick Electric

Units changed from cents to ¢/kWh. This more accurately represents the type of value, and makes the sensor work when used in the Energy dashboards.

If you relied on this unit of measurement format in your automations, scripts, or have been recording it in an external time metrics database, you may need to adapt to this change.

(@ZephireNZ - #69396) (documentation)

History Stats

The pretty formatted value attribute has been removed in favor of using the new duration state class, which is formatted by the frontend.

This change significantly reduces the number of rows stored in the database.

(@bdraco - #70720) (documentation)

HomeKit

The device class carbon_dioxide is no longer admitted as a binary_sensor device class; as it is not a valid device class for a binary sensor. If you have overridden the device class with customize you need to adjust your configuration.

(@epenet - #69239) (documentation)

IKEA TRÅDFRI

The native IKEA TRÅDFRI groups are now removed. We propose using light groups instead.

Additionally, the previously deprecated YAML configuration of the IKEA TRÅDFRI integration has been removed.

IKEA TRÅDFRI 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.

(@ggravlingen - #68033) (documentation)

Integration - Riemann sum integral

The Integration sensor unit configuration parameter was deprecated in Home Assistant Core release 2021.10 and is now removed as it did not take unit_prefix and unit_time into account.

Example:

sensor:
  - platform: integration
    source: sensor.current_power
    name: energy_spent
    unit_prefix: k
    unit_time: h
    unit: MWs
    round: 2

The configuration in the example would cause the source sensor's unit (e.g., W) to be overruled and the integration sensor's unit_of_measurement would be set to MWs (MegaWatt-Second) even though the integral calculation was performed with k (kilo) and h (hour), i.e., the value of the integration sensor is in kWh, not MWs.

(@dgomes - #69157) (documentation)

LIFX

The LIFX integration changed the network adapters used to discover LIFX devices. Instead of enabling all adapters on which LIFX devices appear, it now only uses the adapter(s) enabled in Home Assistant.

This makes the discovery of LIFX faster and more reliable.

(@Djelibeybi - #70458) (documentation)

Media Player

Media Player now supports a new state, buffering. Integrations supporting this state previously reported playing but may now report buffering. This may also introduce new state transitions between the two states during playback.

In order to maintain previous behavior, replace usage of playing with both the buffering and playing states, and consider how to handle transitions between the two.

(@emontnemery - #70863) (documentation)

Media Source

Filenames and directories starting with a . will no longer appear in the Media Browser.

If the file or directory name starts with a ., it means they are marked hidden; thus, the media browser will now respect that.

(@DDanii - #69820) (documentation)

Min/Max

min_max sensors generated a significant amount of database rows because they included all attributes regardless of the configured type. For active sensors, these attributes added up to multiple megabytes per day for each sensor. Reference issue report.

min_max sensors now only set attributes based on the configured type of sensor as below:

• min: min_entity_id
• max: max_entity_id
• last: last_entity_id

The following attributes are no longer present: min, max, mean, median, last, count_sensors

If access to the data previously provided by the attributes is needed, create a separate min_max sensor for that required type instead.

(@bdraco - #70142) (documentation)

MJPEG IP Camera

The previously deprecated YAML configuration of the MJPEG IP Camera integration has been removed.

MJPEG IP Camera 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.

(@frenck - #68033) (documentation)

ONVIF

The previously deprecated YAML configuration of the ONVIF integration has been removed.

ONVIF 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.

(@hunterjm - #70395) (documentation)

Pentair ScreenLogic

The original orp_supply_level and ph_supply_level sensors will become unavailable. Two new sensors will be automatically created, but the originals will have to be removed and the new ones manually renamed to match the originals.

This should only affect those with IntelliChem.

(@dieselrabbit - #69937) (documentation)

Phone Modem

The previously deprecated modem_callerid.reject_call service has now been removed. A button entity has previously been made available as a replacement.

(@frenck - #69019) (documentation)

Radarr

The previously deprecated "Wanted" sensor in the Radarr integration has been removed. If you have this sensor still configured in your YAML configuration, you should remove it before updating.

(@tkdrob - #69500) (documentation)

RainMachine

RainMachine zone switches no longer have the time_remaining attribute; instead, each zone now has a separate sensor entity (device class of timestamp, entity category of diagnostic) that shows the datetime at which the zone will finish (or last finished if the zone isn't running).

(@bachya - #69206) (documentation)

---

RainMachine switch attributes that are floats are now rounded to two decimals of precision.

(@bachya - #70006) (documentation)

Recorder

Home Assistant will now automatically repack your database once a month, on the second Sunday of the month.

Repacking allows shrinking the database in file size, resulting in smaller backups. It also frees up the space that has been freed up by the database optimizations made in 2022.4.

Some notes:

• It is only done once a month to minimize I/O.
• The second Sunday was chosen as it would be out of sync with Home Assistant releases.
• This automatic repacking can be disabled by setting auto_repack to false in the recorder configuration.

(@bdraco - #69314) (documentation)

---

It's no longer possible to configure the recorder to use an in-memory database.

(@emontnemery - #69616) (documentation)

---

Integrations and platforms can provide hints to the recorder to exclude specific entity state attributes from being recorded.

This excludes attributes that hold little to no historical value or are a static value. This significantly reduces the amount of data stored.

The following attributes are no longer recorded:

• Automation: current, id, last_action, last_triggered, max and mode.
• Input Boolean: editable.
• Input Button: editable.
• Input Datetime: editable, has_date, and has_datetime.
• Input Number: editable, max, min, mode, and step.
• Input Text: editable, max, min, mode, and pattern.
• Input Select: editable.

(@bdraco - #70168 #70223)

(@frenck - #70154 #70224 #70225 #70226)

SABnzbd

The SABnzbd integration migrated to configuration via the UI. Configuring SABnzbd 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.

(@shaiu - #68138) (documentation)

Sensibo

The binary sensor for the update available has been removed. Use the new update entities to monitor available updates instead.

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

Sonos

The sonos_group attribute on Sonos media players has been renamed to group_members to align with other integrations.

(@jjlawren - #70924) (documentation)

SQL

The SQL integration migrated to configuration via the UI. Configuring SQL 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.

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

Steam

The Steam integration migrated to configuration via the UI. Configuring Steam 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.

The first account listed in the YAML configuration will be considered as your Steam ID as there is no way to identify your Steam ID from your API key. You can put your Steam ID as the first entry in accounts before updating, or set up the integration from scratch.

(@tkdrob - #67261) (documentation)

Synology DSM

The naming of entities and devices has been aligned, so that the device name is now part of the entity name.

(@mib1185 - #69754) (documentation)

Tautulli

The Tautulli integration migrated to configuration via the UI. Configuring Tautulli 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 - #57450) (documentation)

Templates

Trigger-based template sensors are now initialized to the last known state at Home Assistant startup, instead of to "unknown".

(@emontnemery - #69344) (documentation)

text-to-speech (TTS)

The TTS base_url option is deprecated. Please, configure internal/external URL instead.

(@balloob - #70382) (documentation)

UPnP/IGD

The UPnP/IGD integration options have been removed. This includes the ability to configure a custom update/scan interval.

As an alternative, the more generic and more flexible homeassistant.update_entity service can be used to create an automation that updates the entities on your desired intervals or schedule.

(@StevenLooman - #69134) (documentation)

Vera

Vera power meter sensor is now using the (correct) symbol W for watt instead of watts.

If you relied on this unit of measurement format in your automations, scripts, or have been recording it in an external time metrics database, you may need to adapt to this change.

(@emontnemery - #69285) (documentation)

Z-Wave JS

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.56.
• If you use the Z-Wave JS 2 MQTT add-on, you need to have at least version 0.38.0.
• If you use the zwavejs2mqtt Docker container, you need to have at least version 6.7.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.16.0.

(@raman325 - #70464) (documentation)

Zengge

Zengge lights no longer support white_value, please use white instead.

(@emontnemery - #55260) (documentation)

Farewell to the following

The following integrations are also no longer available as of this release:

• Arlo has been removed. It was in a broken state for a long time caused by authentication changes upstream. (@anaisbetts - #70330)
• Digital Loggers has been removed. It relied on web scraping, which is not allowed for a Home Assistant Core integration. (@tkdrob - #69939)
• Updater was previously deprecated and has been removed. Use the Version and Analytics integrations as a replacement. (@frenck - #68981)

MQTT

Defining manually configured MQTT entities directly under the respective platform keys (e.g., fan, light, sensor, etc.) is deprecated, and support will be removed in Home Assistant Core 2022.9.

Manually configured MQTT entities should now be defined under the mqtt configuration key in configuration.yaml instead of under the platform key.

As an example, this is now deprecated:

sensor:
  - platform: "mqtt"
    name: "My sensor"
    state_topic: "some-state-topic"

The configuration needs to be updated to this format:

mqtt:
  sensor:
    - name: "My sensor"
      state_topic: "some-state-topic"

(@jbouwh - #71676 #72183 #72281 #72249 #72271 #72167 #72165 #72251 #72279 #72268 #72272 #72273 #72274 #72278 #72270) (documentation)

Template filter/function defaults

The following template filters and functions will now error instead of returning the input if the input is invalid and no default value is specified:

• acos
• as_timestamp
• asin
• atan
• atan2
• cos
• float
• int
• log
• multiply
• round
• sin
• sqrt
• strptime
• tan
• timestamp_custom
• timestamp_local
• timestamp_utc

Examples:

• {{ "abc" | float }}: Will fail to render
• {{ "abc" | float(default=5) }}: Will render as 5, no warning will be logged
• {{ float("abc") }}: Will fail to render
• {{ float("abc", default=5) }}: Will render as 5, no warning will be logged

(@emontnemery - #71687) (documentation)

OAuth2 (re-)authentications

Home Assistant will now use My Home Assistant to redirect the OAuth2 callback over.

If you need to re-authenticate with an existing OAuth2 application in the future, you might need to adjust the external application configuration. Please check the documentation of the specific integration on how to configure this.

(@frenck - #72449) (documentation)

Home Assistant Container

If you run Home Assistant Container in Docker (e.g., using Portainer, Docker (Compose), QNAP, and others), please make sure you are not specifying an init process.

This can be an init configuration option in your Docker management tools or Docker Compose, or the --init command line flag on the raw Docker command. These should NOT be set, as Home Assistant ships with the S6 init system.

While you are at it, make sure you also do not set a cmd or entrypoint. Setting these are not breaking, however, you should not set them.

(@pvizeli - #72425) (documentation)

1-Wire

Using the 1-Wire via SysBus, previously deprecated, has been removed; this integration is being adjusted to comply with Architectural Decision Record 0019; more information can be found here:

https://github.com/home-assistant/architecture/blob/master/adr/0019-GPIO.md

ℹ️ Using the 1-Wire via OWServer is still supported!

(@epenet - #71232) (documentation)

Aladdin Connect

The Aladdin Connect integration migrated to configuration via the UI. Configuring Aladdin Connect 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.

(@mkmer - #68304) (documentation)

BMW Connected Drive

The binary_sensor.<your_vehicle>_lights_parking has been removed. It is not provided by API anymore.

The following sensors have been renamed. Existing sensors with historical data and automations should be migrated automatically:

• sensor.<your_vehicle>_charging_level_hv to sensor.<your_vehicle>_remaining_battery_percent
• sensor.<your_vehicle>_fuel_percent to sensor.<your_vehicle>_remaining_fuel_percent

(@rikroe - #71827) (documentation)

Deluge

The previously deprecated YAML configuration of the Deluge integration has been removed.

Deluge 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.

(@tkdrob - #71487) (documentation)

Discord

The previously deprecated YAML configuration of the Discord integration has been removed.

Discord 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.

(@frenck - #71696) (documentation)

DuneHD

The previously deprecated YAML configuration of the DuneHD integration has been removed.

DuneHD 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.

(@frenck - #71694) (documentation)

File Size

The previously deprecated YAML configuration of the File Size integration has been removed.

File Size 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.

(@frenck - #71692) (documentation)

Google Calendars

The configuration of the OAuth application credentials for the Google Calendars integration has migrated to configuration via the UI. Configuring Google Calendars OAuth application credentials via YAML configuration has been deprecated and will be removed in a future Home Assistant release.

Your existing OAuth application credentials in the YAML configuration is automatically imported on upgrade to this release; and thus can be safely removed from your YAML configuration after upgrading.

All entity tracking state has been migrated to use the standard Home Assistant entity enable/disable features in the user interface and system options.

(@allenporter - #72288) (documentation)

---

The found_calendar service has been removed from Google Calendars. This service is an internal implementation detail of the integration used for creating calendars found from the API, which is now no longer exposed as a service.

(@allenporter - #72260) (documentation)

HERE Travel Time

The HERE Travel Time integration migrated to configuration via the UI. Configuring HERE Travel Time 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.

(@eifinger - #69212) (documentation)

Home Connect

The configuration of the OAuth application credentials for the Home Connect integration has migrated to configuration via the UI. Configuring Home Connect OAuth application credentials via YAML configuration has been deprecated and will be removed in a future Home Assistant release.

Your existing OAuth application credentials in the YAML configuration is automatically imported on upgrade to this release; and thus can be safely removed from your YAML configuration after upgrading.

(@allenporter - #71988) (documentation)

Honeywell Lyric

The configuration of the OAuth application credentials for the Honeywell Lyric integration has migrated to configuration via the UI. Configuring Honeywell Lyric OAuth application credentials via YAML configuration has been deprecated and will be removed in a future Home Assistant release.

Your existing OAuth application credentials in the YAML configuration is automatically imported on upgrade to this release; and thus can be safely removed from your YAML configuration after upgrading.

(@allenporter - #72335) (documentation)

International Space Station (ISS)

The previously deprecated YAML configuration of the International Space Station (ISS) integration has been removed.

International Space Station (ISS) 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.

(@frenck - #71693) (documentation)

Jandy iAqualink

The previously deprecated YAML configuration of the Jandy iAqualink integration has been removed.

Jandy iAqualink 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.

(@epenet - #72404) (documentation)

KNX

A new configuration key for KNX covers invert_updown can be set to invert the up-down payload (binary) of covers independently of the position percentage.

Previously up-down (move_long_address) payloads were inverted when invert_position: true was configured. This now only inverts the position_address and position_state_address payloads (%).

If you have used invert_position: true for covers, you would need to add the new key to your YAML config to have the same behaviour as before.

knx:
  cover:
    - name: "Example cover"
      move_long_address: "3/0/0"
      move_short_address: "3/0/1"
      position_address: "3/0/3"
      position_state_address: "3/0/2"
      invert_updown: true  # <- add this line to keep inversion of up/down payload
      invert_position: true

(@farmio - #72012) (documentation)

Litter-Robot

The Litter-Robot vacuum entity will now enter an unavailable state when the robot hasn't sent an update recently.

(@natekspencer - #70810) (documentation)

---

The clean_cycle_wait_time_minutes, status_code, and last_seen attributes have been removed from the vacuum entity as they are now available as individual entities.

(@natekspencer - #71760) (documentation)

Logbook

If the stop and start event were fired within the exact same minute, we would previously show it as restarted in the logbook. When events crossed the minute boundary (i.e., we fired stop at 11:30:59 and start at 11:31:04), it would show separately as stopped and then start.

This change eliminates the inconstancy by always showing them as stopped and started, which allows us to simplify how we generate logbook rows.

(@bdraco - #71600) (documentation)

---

The entity name in the logbook is now always shown with the current name instead of the old name if it was renamed. If the entity no longer exists, we now show the original entity_id instead, which aligns with the warning icon we already display in the frontend when a state is missing or removed.

(@bdraco - #71895) (documentation)

Neato Botvac

The configuration of the OAuth application credentials for the Neato Botvac integration has migrated to configuration via the UI. Configuring Neato Botvac OAuth application credentials via YAML configuration has been deprecated and will be removed in a future Home Assistant release.

Your existing OAuth application credentials in the YAML configuration is automatically imported on upgrade to this release; and thus can be safely removed from your YAML configuration after upgrading.

(@allenporter - #72175) (documentation)

Netatmo

The configuration of the OAuth application credentials for the Netatmo integration has migrated to configuration via the UI. Configuring Netatmo OAuth application credentials via YAML configuration has been deprecated and will be removed in a future Home Assistant release.

Your existing OAuth application credentials in the YAML configuration is automatically imported on upgrade to this release; and thus can be safely removed from your YAML configuration after upgrading.

(@allenporter - #71884) (documentation)

Nexia

The zone status attribute has been removed from the climate entity. The zone status is already available as a separate sensor, and it was producing duplicate data in the state machine.

(@bdraco - #72176) (documentation)

Nexia/American Standard/Trane

Remove non-standard humidify_supported and dehumidify_supported attributes from Nexia.

These attributes can already be inferred from the dehumidify_setpoint or humidify_setpoint attributes.

As they took up space in the database every time any of the values changes, they have now been removed.

(@bdraco - #71248) (documentation)

nVent RAYCHEM SENZ

The configuration of the OAuth application credentials for the nVent RAYCHEM SENZ integration has migrated to configuration via the UI. Configuring nVent RAYCHEM SENZ OAuth application credentials via YAML configuration has been deprecated and will be removed in a future Home Assistant release.

Your existing OAuth application credentials in the YAML configuration is automatically imported on upgrade to this release; and thus can be safely removed from your YAML configuration after upgrading.

(@allenporter - #72338) (documentation)

Recorder

De-duplicate event data into a new event_data table

Data is no longer stored in the event.event_data column and instead deduplicated into the event_data.shared_data column and joined on event.data_id==event_data.data_id.

This is the same as we did with state attributes in 2022.4, as we can reduce the size of the events table by ~8-14% on avg.

(@bdraco - #71135) (documentation)

---

• All the data needed to fetch a state_changed event is now available in the states table (along with state_attributes if needed).
• Reduces overall database size by ~27%
• Refactors logbook to work without the need for the state_changed events rows (fetched from states).
• Refactors purge to work without the need for linking the state_changed event.
• Origin is now stored as an integer.

(@bdraco - #71165) (documentation)

---

The following attributes are no longer recorded for group entities:

• entity_id
• order
• auto

These attributes provide no historical value since they are already contained in the YAML configuration and only fill up the database.

(@bdraco - #71256) (documentation)

---

The recorder now refuses to set up if the database dialect is unsupported or if the database dialect is supported, but the version is too old.

(@emontnemery - #70888) (documentation)

Scrape

The scape integration performance has been improved by using the lxml parser.

Testing (YMMV based on content and nesting):

• For large documents (5000k tags) it was at least an order of magnitude faster.
• For small documents, it was ~3x faster.

Users who are not using Home Assistant Operating System or Home Assistant Container will need to ensure libxml2 and libxslt are installed.

For example, on Debian based Home Assistant Core installs, run: sudo apt install libxml2

(@bdraco - #71087) (documentation)

Slack

The Slack integration migrated to configuration via the UI. Configuring Slack 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 - #69880) (documentation)

Somfy

Somfy has replaced their Somfy Open API (cloud-based) with a local API (which we Home Assistant users absolutely love). Somfy has now decided to shut down its cloud API after June 21st, 2022.

Please migrate to use the Overkiz integration as a replacement.

Unfortunately, a migration to Overkiz is not possible due to differences in the authentication mechanism.

(@iMicknl - #71653) (documentation)

Sonos

The sonos.join and sonos.unjoin services will be removed in 2022.8 in favor of the standard media_player.join and media_player.unjoin services.

(@jjlawren - #71226) (documentation)

Spotify

The configuration of the OAuth application credentials for the Spotify integration has migrated to configuration via the UI. Configuring Spotify OAuth application credentials via YAML configuration has been deprecated and will be removed in a future Home Assistant release.

Your existing OAuth application credentials in the YAML configuration is automatically imported on upgrade to this release; and thus can be safely removed from your YAML configuration after upgrading.

(@allenporter - #71871) (documentation)

Squeezebox (Logitech Media Server)

The Squeezebox player synchronization framework has been updated to use the standard media_player.join and media_player.unjoin services. The list of synchronized players is now stored in the group_members state attribute.

The squeezebox.sync and squeezebox.unsync services are now deprecated, and will be removed in two releases in favor of the standard services listed above.

The sync_group state attribute is deprecated in favor of group_members, and will also be removed in two releases.

(@rajlaud - #70962) (documentation)

Templates

Support for white_value is deprecated in template light and will be removed in Home Assistant Core 2022.9.

(@emontnemery - #71044) (documentation)

Trafikverket Train

The previously deprecated YAML configuration of the Trafikverket Train integration has been removed.

Trafikverket Train 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.

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

Universal Devices ISY994

The auxiliary sensors for each Insteon device are now their own sensor entity instead of an attribute on the parent entity. This makes them easier to find and allows attributes to be de-duplicated in the database.

(@bdraco - #71254) (documentation)

Vera

The Vera integration previously migrated to configuration via the UI. Configuring Vera via YAML configuration has been deprecated and will be removed in a future Home Assistant release.

Your existing YAML configuration has already been automatically imported; and thus can be safely removed from your YAML configuration after upgrading.

(@epenet - #72418) (documentation)

Version

The Boards "Intel NUC", "RaspberryPi" (Raspberry Pi 1 devices), and "RaspberryPi Zero-W" are no longer supported in Home Assistant OS.

They are also no longer available in the version integration. Please remove the version integrations for those boards.

(@agners - #72085) (documentation)

Viessmann ViCare

The previously deprecated YAML configuration of the Viessmann ViCare integration has been removed.

Viessmann ViCare 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.

(@epenet - #72408) (documentation)

Withings

The configuration of the OAuth application credentials for the Withings integration has migrated to configuration via the UI. Configuring Withings OAuth application credentials via YAML configuration has been deprecated and will be removed in a future Home Assistant release.

Your existing OAuth application credentials in the YAML configuration is automatically imported on upgrade to this release; and thus can be safely removed from your YAML configuration after upgrading.

(@allenporter - #71990) (documentation)

WLED

The previously deprecated WLED update button entity has been removed. Please use the newly provided update entity instead.

(@frenck - #71775) (documentation)

Xbox

The configuration of the OAuth application credentials for the Xbox integration has migrated to configuration via the UI. Configuring Xbox OAuth application credentials via YAML configuration has been deprecated and will be removed in a future Home Assistant release.

Your existing OAuth application credentials in the YAML configuration is automatically imported on upgrade to this release; and thus can be safely removed from your YAML configuration after upgrading.

(@allenporter - #71908) (documentation)

Z-Wave JS

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.60.
• If you use the Z-Wave JS 2 MQTT add-on, you need to have at least version 0.41.0.
• If you use the zwavejs2mqtt Docker container, you need to have at least version 6.10.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.17.0.

(@raman325 - #72395) (documentation)

Farewell to the following

The following integrations are also no longer available as of this release:

• Raspberry Pi GPIO has been previously deprecated and now removed. More information can be found in Architectural Decision Record 0019.

Python 3.10

Home Assistant now ships with Python 3.10 for the following installation methods:

• Home Assistant Operating System
• Home Assistant Container
• Home Assistant Supervised

You don't have to do anything; this will all happen automatically. However, this might be a breaking change in case you are using custom integration that does not support Python 3.10 yet.

(@pvizeli - #73830) (documentation)

Bluetooth (multiple integrations)

Home Assistant is upgrading to Python 3.10 this release and comes with a breaking change affecting multiple integrations.

Known affected integrations at the time of writing:

• BeeWi SmartClim BLE sensor
• Bluetooth Tracker
• Elgato Avea
• EQ3 Bluetooth Smart Thermostats
• Leviton Decora
• Mi Flora
• Switchmate SimplySmart Home
• Zengge

These integrations rely on the bluepy and pybluez libraries, which no longer work in newer versions of Python. bluepy has seen its last update in December 2018 and hasn't kept up with changes in the Python world. Similar story with pybluez.

We can't mitigate this issue. If you are using one of these integrations, these will no longer work. We rather wanted to see a non-breaking solution, but we saw no backward compatible path or other solutions to aid this.

If you would like to help fix or upgrade one of these integrations, we would be grateful. We recommend migrating these integrations onto the Bleak library instead.

(@pvizeli - #73830) (documentation)

Entity filters (multiple integrations)

All entity filters, as used by the following integrations:

• Apache Kafka
• Azure Event Hub
• Google Pub/Sub
• History
• InfluxDB
• Logbook
• Recorder

Have been adjusted to make entity filters handle includes stronger than excludes.

Filters are now applied as follows when there are domain and glob includes (may also have excludes):

• Entity listed in entities include: include
• Otherwise, entity listed in entities exclude: exclude
• Otherwise, entity matches glob include: include
• Otherwise, entity matches glob exclude: exclude
• Otherwise, entity matches domain include: include
• Otherwise: exclude

(@bdraco - #74080) (documentation)

Weather (multiple integrations)

This applies to all (weather) integrations providing weather entities.

Previously the units for Weather had not been corresponding correctly with the documentation. These units are now aligned for pressure and wind speed:

• If the unit system is metric, the default pressure unit is hPa, and the default wind speed unit is km/h.
• If the unit system is imperial, the default pressure unit is inHg, and the default wind speed unit is mi/h.

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

Eight Sleep

The Eight Sleep integration migrated to configuration via the UI. Configuring Eight Sleep 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.

(@raman325 - #72570) (documentation)

Glances

The previously deprecated YAML configuration of the Glances integration has been removed.

Glances 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.

(@engrbm87 - #72706) (documentation)

Google Calendars

The Google Calendar google.scan_for_calendars service has been removed. Similar functionality can be achieved with the homeassistant.reload_config_entry service, which will reload the integration and load all new calendars from the API.

(@allenporter - #73010) (documentation)

---

The Google Calendar add_event service is deprecated and will be removed in a future Home Assistant release.

A new service create_event with equivalent functionality is its replacement, which is an entity-based service that takes an entity as a target (rather than a Google Calendar ID).

(@allenporter - #72473) (documentation)

---

Google Calendars no longer supports entity customizations in the UI when google_calendars.yaml specifies the same entity multiple times.

(@allenporter - #73715) (documentation)

Hunter Douglas PowerView

Top Down/Bottom Up shades will now have an entity to control each motor. You will need to manually remove any old entities by selecting the unavailable entities from the Home Assistant Interface, selecting "REMOVE ENTITY", and then confirming the removal by clicking "REMOVE".

• If you have automations to set shade position based on entity ID, you will need to reconfigure these as the new entities will be named differently.
• If you only have automations set to trigger scenes you do not need to reconfigure automations.

(@kingy444 - #62788) (documentation)

Islamic Prayer Times

The previously deprecated YAML configuration of the Islamic Prayer Times integration has been removed.

Islamic Prayer Times 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.

(@engrbm87 - [#7287248332]) (documentation)

Kostal Plenticore

The Kostal Plenticore now has number entities. Two existing sensors entities have been promoted to this platform: "Battery min Soc" and "Battery min Home Consumption".

If you use these sensors entities in your automation, scripts, or dashboards, you will need to adjust these for this change.

(@stegm - #64927) (documentation)

LG Soundbars

The LG Soundbars integration migrated to configuration via the UI. The automatic discovery of the integration via legacy discovery has been removed.

This change has no possible migration path; therefore, if you use this integration, you will have to re-add it manually via the user interface.

(@MasonCrawford - #71153) (documentation)

Life360

Overview

The Life360 integration has been converted from the old "legacy" implementation (which uses known_devices.yaml) to the newer entity based design, similar to what was done back in the 0.94.0 release to many other device tracker integrations.

Due to this change, all your existing Life360 entities will become non-functional, and there will be new entities, with different entity IDs, that are functional.

Steps to replace old entities with new ones

1. Edit the known_devices.yaml file in your configuration directory to

remove any Life360-related entries. Or, if there are only Life360 entries in this file, simply delete the file entirely.

2. Restart Home Assistant. All the old, non-functional Life360 entities

should now be gone. (If you are still seeing the old entities, try refreshing your browser.)

3. Go to the Entities page (under Settings -> Devices & services -> Entities)

and change the entity IDs for the new Life360 entities as desired.

Removed/changed functionality

The previously deprecated YAML configuration of the Life360 integration has been removed.

Life360 is now configured via the UI. Any "advanced" options in YAML configuration will be imported. Once the migration is complete, any life360 entries in YAML configuration should be removed.

The following options are no longer supported:

• circles
• members
• error_threshold
• warning_threshold
• max_update_wait (including the life360_update_overdue & life360_update_restored events)
• show_as_state: moving

Additionally, the following entity attributes have been changed:

• Renamed: battery -> battery_level
• Removed: moving, raw_speed

If you have been using these attributes in your automations or script, you'll need to adapt them to this change.

(@pnbruckner - #72461 #73904) (documentation)

Mazda Connected Services

The start_engine, stop_engine, turn_on_hazard_lights, turn_off_hazard_lights, start_charging, and stop_charging services are removed from the Mazda integration.

They were deprecated in 2022.4 and replaced by button and switch entities.

(@bdr99 - #73403) (documentation)

Met Office

Met Office doesn't provide precise visibility distance, only ranges - i.e., something like "Very good - 20-40 km".

This doesn't fit into the weather entity model, so it's now removed. The old value is still available in a separate sensor provided by this integration.

(@avee87 - #74314) (documentation)

Mikrotik

The previously deprecated YAML configuration of the Mikrotik integration has been removed.

Mikrotik 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.

(@engrbm87 - #72581) (documentation)

MySensors

The previously deprecated YAML configuration of the MySensors integration has been removed.

MySensors 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.

(@MartinHjelmare - #72761) (documentation)

Nest

The Nest authentication method called "Desktop", "Installed App" or "OOB" auth has been deprecated by Google and is scheduled to break existing users in October.

As a result, the Home Assistant Nest integration setup has been streamlined to help make the transition easier for users. See the integration documentation for details.

The configuration of the OAuth application credentials for the Nest integration has migrated to configuration via the UI. Configuring Nest OAuth application credentials via YAML configuration has been deprecated and will be removed in a future Home Assistant release.

If you were already using Web Auth, your existing Nest application credentials in the YAML configuration are automatically imported on upgrade to this release; and thus can be safely removed from your YAML configuration after upgrading.

(@allenporter - #73050) (documentation)

Notifications for Android TV / Fire TV

The previously deprecated YAML configuration of the Notifications for Android TV / Fire TV integration has been removed.

Notifications for Android TV / Fire TV 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.

(@engrbm87 - #73227) (documentation)

NZBGet

The previously deprecated YAML configuration of the NZBGet integration has been removed.

NZBGet 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.

(@epenet - #72424) (documentation)

Radio Thermostat

The Radio Thermostat integration migrated to configuration via the UI. Configuring Radio Thermostat 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.

(@bdraco - #72874) (documentation)

---

Radio Thermostat's hold mode is now configured using a switch. This replaces the original YAML configuration option named hold_temp.

The integration now only synchronizes time when loaded if the hold mode is not active. Synchronizing the time when the hold mode is active causes the hold mode to disable unexpectedly.

(@bdraco - #73104) (documentation)

Scrape

The default scan interval of the scape sensor has been changed from 30 seconds to a more reasonable 10 minutes; This prevents unneeded hammering of websites by default.

(@balloob - #74285) (documentation)