jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-18 14:56:53 +00:00
Code Issues Packages Projects Releases Wiki Activity

2023.6: Finish breaking changes

Browse Source
This commit is contained in:
Franck Nijhof 2023-06-07 12:03:41 +02:00
parent 41420845cd
commit ed9d461505
No known key found for this signature in database
GPG Key ID: D62583BA8AB11CA3
1 changed files with 46 additions and 35 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

81
source/_posts/2023-06-07-release-20236.markdown
View File

@ -492,17 +492,9 @@ other news about building an Open Home; straight into your inbox.
## Breaking Changes ## Breaking Changes
{% details "TODO" %}
- Proof read/spelling/grammar
**Note**: Breaking changes processed up to PR 92223
{% enddetails %}
{% details "Python" %} {% details "Python" %}
All Home Assistant versions of which the Home Assistant project manages the 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 Python version for you, have been upgraded to Python 3.11. This affects
the following installation types: the following installation types:
@ -510,16 +502,16 @@ the following installation types:
- Home Assistant Container - Home Assistant Container
- Home Assistant Supervised - Home Assistant Supervised
This might affect you when you are using custom integrations, as those have This might affect you when using custom integrations, as those must be
to be compatible with Python 3.11. compatible with Python 3.11.
Furthermore, as of this release, Python 3.10 is deprecated and support will 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 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 running Home Assistant Core installation type in your own Python virtual
environment. Please update your Python version to Python 3.11. environment. Please update your Python version to Python 3.11.
If you run Home Assistant OS, Home Assistant Container or Home Assistant 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 Supervised, we have taken care of this for you; you will be using Python 3.11
automatically on upgrade. automatically on upgrade.
{% enddetails %} {% enddetails %}
@ -527,8 +519,8 @@ automatically on upgrade.
{% details "APC UPS Daemon" %} {% details "APC UPS Daemon" %}
`sensor.ups_self_test_interval` sensor now properly splits unit "days" from the `sensor.ups_self_test_interval` sensor now properly splits unit "days" from the
raw data. Previously, it will show `7 days` as sensor state, now it shows `7` raw data. Previously, it would show `7 days` as the sensor state.
with a unit "Days". Now it shows `7` with a unit "Days".
([@yuxincs] - [#93844]) ([documentation](/integrations/apcupsd)) ([@yuxincs] - [#93844]) ([documentation](/integrations/apcupsd))
@ -540,9 +532,9 @@ with a unit "Days".
{% details "Counter" %} {% details "Counter" %}
The `counter` entities no longer restore their previous manually set The `counter` entities no longer restore their previous manually set
configuration (using the, now deprecated, `counter.configure` service) on configuration (using the - now deprecated - `counter.configure` service) on
Home Assistant startup. Instead, it will now use the configuration as set in Home Assistant startup. Instead, it will now use the configuration as set in
the helper configuration in the UI (or as configured YAML, if that is used). the helper configuration in the UI (or as configured YAML, if used).
This behavior is removed, as it caused configuration issues, as the new This behavior is removed, as it caused configuration issues, as the new
configuration was never applied again (but forever restored). This behavior was configuration was never applied again (but forever restored). This behavior was
@ -592,8 +584,8 @@ removed from your YAML configuration files.
{% details "EZVIZ" %} {% details "EZVIZ" %}
The binary sensor providing "upgrade available" information, has been removed The binary sensor providing "upgrade available" information has been removed
and replaced by a new `update` entity. If you used the binary sensor in your 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 automations, scripts, or dashboards, you will need to adjust them to
this change. this change.
@ -641,9 +633,9 @@ Home Assistant was still using the legacy Python pip package resolver, which
has been removed. Due to upstream package conflicts, the IBM Watson TTS has been removed. Due to upstream package conflicts, the IBM Watson TTS
integration has been disabled. integration has been disabled.
The upstream project providing the libaries used, has been notified repeatedly The upstream project providing the libraries used has been notified repeatedly
in, at least, the past two years; unfortunately, without response. We had no in, at least, the past two years; unfortunately, without response. We had no
other choice than disabling this integration. other choice to disable disabling this integration.
([@frenck] - [#92124]) ([documentation](/integrations/watson_tts)) ([@frenck] - [#92124]) ([documentation](/integrations/watson_tts))
@ -654,13 +646,13 @@ other choice than disabling this integration.
{% details "IHC Controller" %} {% details "IHC Controller" %}
The default unit of measurement for manually set up sensors from IHC have been The default unit of measurement for manually set up sensors from IHC has been
removed. Home assistant now assume all sensors with unit of measurement set is removed. Home Assistant now assume all sensors with a unit of measurement set
a number. IHC sensors can be text, but because of the default unit of 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. 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 This is a breaking fix because if you currently have temperature sensors
without unit of measurement set, you will have to set this for the sensors. without a unit of measurement set, you will have to set this for the sensors.
([@dingusdk] - [#91096]) ([documentation](/integrations/ihc)) ([@dingusdk] - [#91096]) ([documentation](/integrations/ihc))
@ -671,8 +663,8 @@ without unit of measurement set, you will have to set this for the sensors.
{% details "LG Netcast" %} {% details "LG Netcast" %}
LG Netcast media player do no longer have fake (assumed) `playing` or `paused` LG Netcast media players no longer have fake (assumed) `playing` or `paused`
states and those are replaced with the `on` state. states, and those are replaced with the `on` state.
If you used the `playing` or `paused` state in your automations, you will need If you used the `playing` or `paused` state in your automations, you will need
to update them to match this change. to update them to match this change.
@ -686,9 +678,9 @@ to update them to match this change.
{% details "Meteorologisk institutt (Met.no)" %} {% details "Meteorologisk institutt (Met.no)" %}
The weather forecast provided by the weather entity has changes. The current The weather forecast provided by the weather entity has changed. The current
day has been added to the forecast. If your automation or scripts relied day has been added to the forecast. If your automation or scripts relied
on the first day to be tomorrow, you will need to adjust. on the first day to be tomorrow, you would need to adjust.
([@mmalina] - [#91891]) ([documentation](/integrations/met)) ([@mmalina] - [#91891]) ([documentation](/integrations/met))
@ -752,6 +744,15 @@ that we no longer create an entity for each persistent notification.
[@bdraco]: https://github.com/bdraco [@bdraco]: https://github.com/bdraco
[#92828]: https://github.com/home-assistant/core/pull/92828 [#92828]: https://github.com/home-assistant/core/pull/92828
---
The `persistent_notification.mark_read` service has been removed.
([@bdraco] - [#94122]) ([documentation](/integrations/persistent_notification))
[@bdraco]: https://github.com/bdraco
[#94122]: https://github.com/home-assistant/core/pull/94122
{% enddetails %} {% enddetails %}
{% details "Rain Bird" %} {% details "Rain Bird" %}
@ -786,9 +787,9 @@ Home Assistant was still using the legacy Python pip package resolver, which
has been removed. Due to upstream package conflicts, the Salda Smarty has been removed. Due to upstream package conflicts, the Salda Smarty
integration has been disabled. integration has been disabled.
The upstream project providing the libaries used, has been notified repeatedly The upstream project providing the libraries used has been notified repeatedly
in, at least, the past two years; unfortunately, without response. We had no in, at least, the past two years; unfortunately, without response. We had no
other choice than disabling this integration. other choice than to disable this integration.
([@frenck] - [#92124]) ([documentation](/integrations/smarty)) ([@frenck] - [#92124]) ([documentation](/integrations/smarty))
@ -815,7 +816,7 @@ removed from your YAML configuration files.
{% details "Total Connect" %} {% details "Total Connect" %}
The tampered and low battery status zone attribute have been moved into their 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, 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. scripts, or dashboards, you will need to update those to reflect this change.
@ -829,7 +830,7 @@ scripts, or dashboards, you will need to update those to reflect this change.
{% details "Universal Devices ISY/IoX" %} {% details "Universal Devices ISY/IoX" %}
The previously deprecated sensor entities for Insteon devices' On Level and 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 Ramp Rate, as well as ISY Variable sensors, have been removed. Please use the
dedicated `number` and `select` entities instead. dedicated `number` and `select` entities instead.
([@shbatm] - [#92255]) ([documentation](/integrations/isy994)) ([@shbatm] - [#92255]) ([documentation](/integrations/isy994))
@ -902,6 +903,16 @@ changes and new features available for your integration: Be sure to follow our
[devblog]: https://developers.home-assistant.io/blog/ [devblog]: https://developers.home-assistant.io/blog/
## 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])
[@thecode]: https://github.com/thecode
[#94129]: https://github.com/home-assistant/core/pull/94129
## All changes ## All changes
Of course, there is a lot more in this release. You can find a list of Of course, there is a lot more in this release. You can find a list of