Home Assistant Core 2023.7.0 → 2023.8.0

Python 3.10 support has been removed

Python 3.10 support has previously been deprecated and has now been removed. Home Assistant now requires Python 3.11 to run.

You don't have to do anything if you are using Home Assistant OS, Home Assistant Container, or Home Assistant Supervised installation method. In those cases, we handle this all for you.

Your system has been using Python 3.11 for quite some time already.

(@frenck - #97007)

Discovery

The legacy discovery integration has been removed. This only affects the automatic discovery of Enigma2, Yamaha Network Receivers, and Bluesound.

These can still be manually configured as per usual.

Note this is for our very, very old discovery logic. This does not affect the discovery of any other integration/device/service.

If you still have discovery: listed in your YAML configuration, you can safely remove it.

(@frenck - #96856)

Ecovacs

The Ecovacs integration has been migrated to the new "StateVacuumEntity" under the hood.

The states of the vacuum entity now report not only on or off, instead cleaning, paused, docked (implicit mean charging), returning (to base), idle and error. Further, the actions turn_on (start cleaning), and turn_off (stop cleaning and return to base) were superseded by three single actions start, stop and return_to_base.

(@mib1185 - #95920) (documentation)

Google Nest

The legacy Works With Nest API is no longer supported. You must manually take action to use the SDM API by removing the Nest configuration from configuration.yaml and restarting Home Assistant. Then add the Nest integration following the instructions. Please review the documentation for information about which devices are supported.

Additionally, as a reminder, the legacy Works With Nest API is shutting down in September 2023.

(@allenporter - #96111) (documentation)

MQTT

It's no longer allowed for an MQTT RGB light without a brighness_state_topic to report an RGB value of RGB=0,0,0. The reason is that for such lights, the light's brightness is derived from the RGB value, and an RGB value of RGB=0,0,0 corresponds to a brightness of 0 which is not allowed.

In case an MQTT RGB light without a brighness_state_topic reports 0,0,0 for R, G, and B, that update will be ignored.

(@jbouwh - #96286) (documentation)

---

The MQTT climate CONF_POWER_STATE_TOPIC and CONF_POWER_STATE_TEMPLATE were deprecated in HA Core 2023.2.0 and are now removed. Please remove these options from your configuration. The options were not implemented but will break your MQTT configuration if they are still present in your config.

(@jbouwh - #96771) (documentation)

---

The way MQTT entities are named and how device configuration can be shared between discovered entities has changed.

Sharing of device configuration

Discovered MQTT entities can share device configuration, meaning one entity can include the full device configuration, and other entities can link to that device by only setting mandatory fields.

The mandatory fields were previously limited to at least one of connection and identifiers, but have now been extended to at least one of connection and identifiers as well as the name.

Naming of MQTT entities

The naming of MQTT entities has been changed to be aligned with the entity naming guidelines:

• The has_entity_name entity will be set to True on all MQTT entities.
• This means any MQTT entity which is part of a device will automatically have its friendly_name attribute prefixed with the device name.
• Unnamed binary_sensor, button, event, number, and sensor entities will now be named by their device class instead of being named "MQTT binary sensor" etc.
• It's now allowed to set an MQTT entity's name to None to mark it as the main feature of a device.

(@jbouwh - #95159) (documentation)

Philips Dynalite

The Dynalite configuration panel, which previously was on the Home Assistant sidebar, has moved. It can now be accessed via the integration page in Settings > Device & services > Dynalite > Configure.

(@frenck - #95920) (documentation)

Renson

The state values of the Reason Ventilation integration have been changed to be more consistent with other integrations and are now lowercase. Additionally, it can now provide translations for the state values in the UI.

This means that the following state values have changed:

• Off -> off
• Level1 -> level1
• Level2 -> level2
• Level3 -> level3
• Level4 -> level4
• Breeze -> breeze
• Holiday -> holiday

Please update any automations where you are using the state of this Renson sensor.

Farewell to the following

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

• Discovery has been removed. This is the old legacy discovery integration. See the backward-incompatible changes above for more information. (@frenck - #96856)
• Mi Flora has been removed. This integration was replaced by the Xiaomi BLE integration a long time ago and was in a non-functional state. (@frenck - #96868)
• Xiaomi Mijia BLE T&H Sensor has been removed. This integration was replaced by the Xiaomi BLE integration a long time ago and was in a non-functional state. (@frenck - #96869)