2024.7: Finalize backward-incompatible changes

This commit is contained in:
Franck Nijhof 2024-07-03 11:20:23 +02:00
parent ba74884f38
commit e28d7606fe
No known key found for this signature in database
GPG Key ID: D62583BA8AB11CA3

View File

@ -573,7 +573,7 @@ corrected from `c` to `¢/kWh`.
{% details "DNS IP" %} {% details "DNS IP" %}
The attribute names `Resolver` and `Querytype` have been renamed to The attribute names `Resolver` and `Querytype` have been renamed to
`resolver` and `querytype`. If ause these in any automation or script, `resolver` and `querytype`. If you use these in any automations or scripts,
you need to update them to use the new lowercase names. you need to update them to use the new lowercase names.
([@gjohansson-ST] - [#119727]) ([documentation](/integrations/dnsip)) ([@gjohansson-ST] - [#119727]) ([documentation](/integrations/dnsip))
@ -609,7 +609,7 @@ to refresh and run a speedtest manually instead.
{% details "Intergas InComfort/Intouch Lan2RF gateway" %} {% details "Intergas InComfort/Intouch Lan2RF gateway" %}
Based on the boiler display code or fault code, the boiler status Based on the boiler display code or fault code, the boiler status
has been refactored to be signified and unique, so we can start supporting has been refactored to be signified and unique so we can start supporting
localization. localization.
Depending on the old status texts, automations or scripts might break. Depending on the old status texts, automations or scripts might break.
@ -740,7 +740,7 @@ Assistant. This was a virtual code that was not used by the SimpliSafe system.
An SQL query generating several columns output was putting the additional An SQL query generating several columns output was putting the additional
attributes on the SQL sensor. attributes on the SQL sensor.
From now on these are still shown as state attributes but are no longer From now on, these are still shown as state attributes but are no longer
recorded in the database as attributes on this particular sensor recorded in the database as attributes on this particular sensor
(as the data for these attributes are already present in the database (as the data for these attributes are already present in the database
from where they come). from where they come).
@ -766,9 +766,9 @@ information, so that sensor is no longer available.
{% details "Swiss public transport" %} {% details "Swiss public transport" %}
Swiss public transport does not provide additional state attributes anymore; Swiss public transport no longer provides additional state attributes; since
all information has been moved to dedicated individual sensors since the the release of Home Assistant 2023.12, all information has been moved to
release of Home Assistant 2023.12. dedicated individual sensors.
([@miaucl] - [#120256]) ([documentation](/integrations/swiss_public_transport)) ([@miaucl] - [#120256]) ([documentation](/integrations/swiss_public_transport))
@ -779,7 +779,7 @@ release of Home Assistant 2023.12.
{% details "Tami4 Edge / Edge+" %} {% details "Tami4 Edge / Edge+" %}
Due tue upstream API changes, the UV & filter's last replaced date has been Due to upstream API changes, the UV & filter's last replaced date has been
removed. removed.
Additionally, `uv_status` & `filter_status` sensor entities have been changed Additionally, `uv_status` & `filter_status` sensor entities have been changed
@ -825,7 +825,7 @@ Note that these values are constant throughout the lifetime of a utility meter.
{% details "Weather" %} {% details "Weather" %}
Weather service `get_forecast` was deprecated in favor of `get_forecasts` in Weather service `get_forecast` was deprecated in favor of `get_forecasts` in
Home Assistant 2023.12, and has now been removed. Home Assistant 2023.12 and has now been removed.
Use the new `get_forecasts` service to retrieve forecast information Use the new `get_forecasts` service to retrieve forecast information
from `weather` entities instead. from `weather` entities instead.