Home Assistant Core 2023.5.0 → 2023.6.0

Python

All Home Assistant versions, of which the Home Assistant project manages the Python version for you, have been upgraded to Python 3.11. This affects the following installation types:

• Home Assistant Operating System
• Home Assistant Container
• Home Assistant Supervised

This might affect you when using custom integrations, as those must be compatible with Python 3.11.

Furthermore, as of this release, Python 3.10 is deprecated, and support will be removed in Home Assistant 2023.8. This only affects you if you are running Home Assistant Core installation type in your own Python virtual environment. Please update your Python version to Python 3.11.

If you run Home Assistant OS, Home Assistant Container, or Home Assistant Supervised, we have taken care of this for you; you will be using Python 3.11 automatically on upgrade.

APC UPS Daemon

sensor.ups_self_test_interval sensor now properly splits unit "days" from the raw data. Previously, it would show 7 days as the sensor state. Now it shows 7 with a unit "Days".

(@yuxincs - #93844) (documentation)

Counter

The counter entities no longer restore their previous manually set configuration (using the - now deprecated - counter.configure service) on Home Assistant startup. Instead, it will now use the configuration as set in the helper configuration in the UI (or as configured YAML, if used).

This behavior is removed, as it caused configuration issues, as the new configuration was never applied again (but forever restored). This behavior was out of the ordinary for Home Assistant and thus now standardized.

The value of the counter is still restored and available across Home Assistant restarts.

(@frenck - #93344) (documentation)

Command Line

The Command Line integration changes its YAML configuration format from an old-style platform configuration to a more modern integration-style configuration format.

For example, if you have a binary sensor configured previously as:

# Example configuration.yaml entry
binary_sensor:
  - platform: command_line
    command: "cat /proc/sys/net/ipv4/ip_forward"

That same binary sensor is now configured under the command_line integration configuration as:

# Example configuration.yaml entry
command_line:
  - binary_sensor:
      command: "cat /proc/sys/net/ipv4/ip_forward"

Note: While this is currently not yet a breaking change, it did raise questions during our beta testing period. Hence we have added this as a breaking change to provide more context.

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

D-Link Wi-Fi Smart Plugs

The previously deprecated YAML configuration of the D-Link Wi-Fi Smart Plugs integration has been removed.

D-Link Wi-Fi Smart Plugs are 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 - #92590) (documentation)

EDL21

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

EDL21 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 - #93551) (documentation)

EZVIZ

The binary sensor providing "upgrade available" information has been removed and replaced by a new update entity. If you use the binary sensor in your automations, scripts, or dashboards, you will need to adjust them to this change.

(@RenierM26 - #85377) (documentation)

Frontier Silicon

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

Frontier Silicon 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 - #93552) (documentation)

Google Nest

The Google Nest YAML configuration has been fully removed. You should ensure you have imported your configuration and credentials into the UI before upgrading.

Nest Desktop or OOB authentication, which was previously disabled by Google, has now been removed.

(@allenporter - #92311) (documentation)

IBM Watson TTS

Home Assistant was still using the legacy Python pip package resolver, which has been removed. Due to upstream package conflicts, the IBM Watson TTS integration has been disabled.

The upstream project providing the libraries used has been notified repeatedly in, at least, the past two years; unfortunately, without response. We had no other choice than to disable this integration.

(@frenck - #92124) (documentation)

IHC Controller

The default unit of measurement for manually set up sensors from IHC has been removed. Home Assistant now assumes all sensors with a unit of measurement set are a number. IHC sensors can be text, but because of the default unit of measurement, there is currently no way to get text sensors from IHC working.

This is a breaking fix because if you currently have temperature sensors without a unit of measurement set, you will have to set this for the sensors.

(@dingusdk - #93054) (documentation)

LG Netcast

LG Netcast media players no longer have fake (assumed) playing or paused states, and those are replaced with the on state.

If you used the playing or paused state in your automations, you will need to update them to match this change.

(@Drafteed - #93543) (documentation)

Meteorologisk institutt (Met.no)

The weather forecast provided by the weather entity has changed. The current day has been added to the forecast. If your automations or scripts rely on the first day to be tomorrow, you need to adjust them.

(@mmalina - #91891) (documentation)

MQTT

MQTT sensor configurations that still use last_reset_topic will fail. The support was deprecated in Home Assistant 2021.11 and is now removed. Users should use last_reset_value_template instead.

(@jbouwh - #93792) (documentation)

Nextcloud

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

Nextcloud 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 - #93550) (documentation)

Obihai

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

Obihai 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 - #93549) (documentation)

Persistent notifications

Persistent notifications are no longer stored in the state machine. This means that we no longer create an entity for each persistent notification.

If you used these entities in, for example, automations, scripts, or templates, you won't be able to use these anymore.

(@bdraco - #92828) (documentation)

---

The persistent_notification.mark_read service has been removed.

(@bdraco - #94122) (documentation)

Rain Bird

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

Rain Bird 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 - #92599) (documentation)

---

The previously deprecated rainbird.rain_delay service for Rainbird has been removed. Please update any automation or script depending on this service.

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

Salda Smarty

Home Assistant was still using the legacy Python pip package resolver, which has been removed. Due to upstream package conflicts, the Salda Smarty integration has been disabled.

The upstream project providing the libraries used has been notified repeatedly in, at least, the past two years; unfortunately, without response. We had no other choice than to disable this integration.

(@frenck - #92124) (documentation)

Samsung Smart TV

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

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

(@epenet - #93392) (documentation)

Total Connect

The tampered and low battery status zone attributes have been moved into their own dedicated binary sensors. If you use these attributes in your automations, scripts, or dashboards, you will need to update those to reflect this change.

(@austinmroczek - #73152) (documentation)

Universal Devices ISY/IoX

The previously deprecated sensor entities for Insteon devices' On Level and Ramp Rate, as well as ISY Variable sensors, have been removed. Please use the dedicated number and select entities instead.

(@shbatm - #92255) (documentation)

Vallox

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

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

(@slovdahl - #91096) (documentation)

Z-Wave

On/Off properties for the Indicator CC are no longer discovered as entities.

They were previously discovered as sensor entities which were not useful in cases where you wanted to change these values, and you would need to change the value for all three On/Off properties simultaneously in order for them to work, which wasn't supported with our existing discovery model.

(@raman325 - #90248) (documentation)

---

For devices with the Entry control generic device class, the Door lock mode config parameter no longer gets created as a sensor entity and will instead get created as a select entity.

(@raman325 - #92223) (documentation)

---

The Nice IBT4ZWAVE module was previously discovered as a light, but now it is discovered as a cover. The light entity will be permanently unavailable and can be safely deleted.

(@raman325 - #93946) (documentation)

---

If you have zwave_js cover entities already and your device supports Window Covering CC, you may see newly created cover entities. The old cover entities can safely be deleted, but all customizations must be reapplied to the new entities.

(@raman325 - #93314) (documentation)

Farewell to the following

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

• Goalfeed has been removed. Their service has been discontinued. (@thecode - #94129)