2022.7: A stunning performance

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)

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)

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)

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)

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)

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)

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)

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)

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)

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)

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)

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)

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

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)

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)

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)

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)

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)

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)

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)

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

(@engrbm87 - #73471) (documentation)

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

After upgrading, each Skybell will now have a device for each doorbell. Also, it has become unnecessary to prefix all entities with “SkyBell”, this may change you existing entities after upgrading and you need to adjust your automation, scripts and dashboard for this change.

(@tkdrob - #70887) (documentation)

---

The following SkyBell entity attributes have been split out into their own sensors: last motion event, last button event, last check-in, motion threshold, video profile, Wi-Fi SSID, Wi-Fi status.

If you rely on these attributes in your automations or scripts, you will need to adapt them to this change.

(@tkdrob - #73089) (documentation)

The following power entity attributes from the climate entity for SmartThings Air Conditioner have been removed and added as separate sensors:

• power_consumption_start
• power_consumption_end
• power_consumption_power
• power_consumption_energy

If you currently use these attributes in your automation or scripts, you’ll need to adapt them to this change.

(@mbo18 - #72594) (documentation)

GSM signal sensor entity was replaced with a set of more granular ones. The old entity will become unavailable after updating to this release.

(@PaulAnnekov - #70486) (documentation)

• This integration now requires System Bridge 3.1.2 and above. Any older version will no longer work.
• BIOS Version, Idle, System, and User Load sensors have been removed. These are no longer available from System Bridge data modules.
• Command service has been removed. This has been removed from System Bridge due to potential security issues.
• Open path and URL are now separate services. If you are using the old system_bridge.open service, you will need to update your automation to use the new service(s).
• GPU entities are from a new source, so they may have changed names slightly. Any automations using these entities may need to be updated.
• GPU fan speed is now measured in RPM instead of %.

(@timmo001 - #71218) (documentation)

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

Tautulli 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 - #74172) (documentation)

---

Entity attributes of Tautulli entities have now been moved to their own sensors.

If you currently use these attributes in your automation or scripts, you’ll need to adapt them to this change.

(@tkdrob - #71712) (documentation)

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

Transmission 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 - #72832) (documentation)

The new disk sensors pull from completely different data than the old ones. They should be largely compatible for functionality, but orphaned sensors may still be created. Any orphaned sensors can be safely deleted.

The sensors’ naming format has also changed to match what is shown in UniFi Protect. Additionally, the extra state attribute for the model has been completely removed since now the slot numbers match what UniFi Protect displays.

(@AngellusMortis - #73104) (documentation)

---

Entities that provided an “edit” configuration interface for Protect devices (like the HDR Switch or Recording Mode Select) have all now been replaced by regular sensor entities; if you do not have write access to that UniFi Protect Device.

These switches, select entities, etc., never actually worked previously since the user did not have permission to change them, but you could read the status.

Any entities that are orphaned by this can be safely deleted.

(@AngellusMortis - #73765) (documentation)

An “order of importance” between the states of the children of Universal Media Player has been added. The active media player might change if some of the children are in “playing” and “paused” states, depending on the children’s order.

(@koying - #68036) (documentation)

The previously deprecated YAML configuration of the UPnP/IGD integration has been removed.

UPnP/IGD 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 - #72410) (documentation)

The air_quality and filter_life attributes have been removed from the fan entities. Dedicated sensor entities have replaced these attributes.

If you are currently using these attributes in your automation or scripts, you’ll need to adapt them to this change.

(@jetpacktuxedo - #72658) (documentation)

---

Vesync switches that support energy monitoring will have their:

• Voltage attribute moved from the switch entity to a dedicated Voltage Sensor entity
• Weekly, monthly and yearly moved from the switch entity attributes into new energy sensors.

If you used these entity attributes in your automation or scripts, you’d need to adapt them to this change.

(@b3nj1 - #72570) (documentation)

With this release, you will need to update your zwave-js-server instance.

• If you use the zwave_js add-on, you need at least version 0.1.64.
• If you use the Z-Wave JS 2 MQTT add-on, you need at least version 0.44.0.
• If you use the zwavejs2mqtt Docker container, you need at least version 6.13.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.20.0.

(@raman325 - #73707 #73904) (documentation)