@@ -76,7 +76,7 @@ Since the last release we have moved all Home Assistant source code etc into its
[Wink]: /integrations/wink#light
[Zeroconf]: /integrations/zeroconf/
-### Breaking changes
+### Backward-incompatible changes
- We have migrated our datetime format to be iso8601. This will only impact you if you are consuming the date times from the API directly. You can ignore this if you are just using Home Assistant via configuration and the frontend.
- The constant `TEMP_CELCIUS` is now correctly called `TEMP_CELSIUS`. Old one is deprecated and will eventually be removed.
- The location of the Docker image has changed. There was no possibility for us to keep maintaining the old image (as it was bound to the GitHub repo under my name) or to make a redirect. So if you are using the Home Assistant Docker image, change it to run `homeassistant/home-assistant:latest` for the latest release and `homeassistant/home-assistant:dev` for the latest dev version.
diff --git a/source/_posts/2016-05-21-release-020.markdown b/source/_posts/2016-05-21-release-020.markdown
index 4c02157bf94..e93fdc16a55 100644
--- a/source/_posts/2016-05-21-release-020.markdown
+++ b/source/_posts/2016-05-21-release-020.markdown
@@ -37,7 +37,7 @@ Tons of new supported things in 0.20.
- Export to [Logentries] support added ([@omgapuppy])
- Group more info dialog allows control of group domain if available (@fignuts)
-### Breaking changes
+### Backward-incompatible changes
- Asus WRT will now default to SSH with Telnet being an option
diff --git a/source/_posts/2016-06-08-super-fast-web-enocean-lirc.markdown b/source/_posts/2016-06-08-super-fast-web-enocean-lirc.markdown
index ea4314df5d3..07760cc74b6 100644
--- a/source/_posts/2016-06-08-super-fast-web-enocean-lirc.markdown
+++ b/source/_posts/2016-06-08-super-fast-web-enocean-lirc.markdown
@@ -37,7 +37,7 @@ Alright, time for the changes:
- Sensor: [DTE Energy Bridge] now supported ([@kylehendricks])
- Media Player: [Kodi] now supports different turn off commands ([@armills])
-### Breaking Changes
+### Backward-incompatible changes
- Our work in the WSGI stack is not fully done yet. We still have a minor issues where retrieving the error log in the about screen can raise an encoding error
- The API used to incorrectly accept a JSON body with form-url-encoded headers. Our cURL examples on the website used to be wrong and have [been updated].
diff --git a/source/_posts/2016-07-01-envisalink-homematic-hdmi-cec-and-sony-bravia-tv.markdown b/source/_posts/2016-07-01-envisalink-homematic-hdmi-cec-and-sony-bravia-tv.markdown
index fc78c91175f..82265807377 100644
--- a/source/_posts/2016-07-01-envisalink-homematic-hdmi-cec-and-sony-bravia-tv.markdown
+++ b/source/_posts/2016-07-01-envisalink-homematic-hdmi-cec-and-sony-bravia-tv.markdown
@@ -44,7 +44,7 @@ On the config side, you can now [store your passwords][secrets] in your OS keyri
- Lock: [Vera] now supported ([@rhooper])
- HTTP: Migrate to CherryPy WSGI server to fix install and runtime problems ([@balloob])
-### Breaking changes
+### Backward-incompatible changes
- Homematic thermostat configuration has changed and now depends on the new [Homematic] component.
diff --git a/source/_posts/2016-07-16-sqlalchemy-knx-join-simplisafe.markdown b/source/_posts/2016-07-16-sqlalchemy-knx-join-simplisafe.markdown
index 2a6eaf58e59..e8afd729c63 100644
--- a/source/_posts/2016-07-16-sqlalchemy-knx-join-simplisafe.markdown
+++ b/source/_posts/2016-07-16-sqlalchemy-knx-join-simplisafe.markdown
@@ -51,7 +51,7 @@ You can omit the `--config` option if you use the default configuration director
Quick hot fix after we found a bug in the migrator where it wouldn't work with a database in a non-standard location. Thanks to [@n8henrie] and [@AlucardZero].
-### Breaking changes
+### Backward-incompatible changes
- Migrating existing databases (see above).
- The [APCUPSd Sensor][apcupsd-sensor] was updated. This will need that you modify your `configuration.yaml` file.
diff --git a/source/_posts/2016-07-30-custom-frontend-panels--jupyter-notebooks--directv.markdown b/source/_posts/2016-07-30-custom-frontend-panels--jupyter-notebooks--directv.markdown
index 682a060920e..3f06ef46985 100644
--- a/source/_posts/2016-07-30-custom-frontend-panels--jupyter-notebooks--directv.markdown
+++ b/source/_posts/2016-07-30-custom-frontend-panels--jupyter-notebooks--directv.markdown
@@ -68,7 +68,7 @@ I would like to do a shoutout to [@fabianhjr]. He has started adding [typing] da
- Hotfix to make sure Z-Wave locks work again. Thanks to @tobiebooth for the quick fix.
-### Breaking changes
+### Backward-incompatible changes
- Google Voice SMS notification support was removed.
diff --git a/source/_posts/2016-08-13-foursquare-fast-com-ffmpeg-gpsd.markdown b/source/_posts/2016-08-13-foursquare-fast-com-ffmpeg-gpsd.markdown
index d611d24a84c..4043c3b2c8a 100644
--- a/source/_posts/2016-08-13-foursquare-fast-com-ffmpeg-gpsd.markdown
+++ b/source/_posts/2016-08-13-foursquare-fast-com-ffmpeg-gpsd.markdown
@@ -58,7 +58,7 @@ This release includes code contributed by 31 different people. The biggest chang
- Media Player cover art would not work when an API password was set. Thanks to [@maddox] for reporting it and [@balloob] for the fix.
-### Breaking changes
+### Backward-incompatible changes
- A new unit system has superseded the temperature unit option in the core configuration. For now it is backwards compatible, but you should update soon:
diff --git a/source/_posts/2016-08-27-notifications-hue-fake-unification.markdown b/source/_posts/2016-08-27-notifications-hue-fake-unification.markdown
index 05d7dd5cc0a..b4c2667ec4e 100644
--- a/source/_posts/2016-08-27-notifications-hue-fake-unification.markdown
+++ b/source/_posts/2016-08-27-notifications-hue-fake-unification.markdown
@@ -46,7 +46,7 @@ Now that we have that great news out of the way, onto this week's release which
## 0.27
-While this release is **#Amazing**, we had to break a few eggs (now you understand the title reference!) to make a beautiful omelette (using home automation obviously) so some platforms and components have needed to introduce breaking changes. Please make sure to read the [Breaking Changes](#breaking-changes) section below.
+While this release is **#Amazing**, we had to break a few eggs (now you understand the title reference!) to make a beautiful omelette (using home automation obviously) so some platforms and components have needed to introduce backward-incompatible changes. Please make sure to read the [Backward-incompatible changes](#backward-incompatible-changes) section below.
### Hue Bridge Emulation
@@ -137,7 +137,7 @@ Along with the new `climate` component, [@Teagan42] and I ([@robbiet480]) decide
- Allow emulating a [Hue] bridge to control entities ([@mgbowen])
- New [Fan][fan] component ([@Teagan42], [@robbiet480])
-### Breaking changes
+### Backward-incompatible changes
- Ecobee3 occupancy sensors have moved from sensor platform to binary sensor platform.
- Forecast.io entity IDs are now like `sensor.forecastio_temperature`. Previously they were like `sensor.weather_temperature`. Apologies for this change, but we needed to make Forecast.io more generic now that we have many weather platforms.
- The [Loop Energy][Loop] sensor configuration format changed slightly, please reformat based on the revised documentation.
diff --git a/source/_posts/2016-09-10-notify-group-reload-api-pihole.markdown b/source/_posts/2016-09-10-notify-group-reload-api-pihole.markdown
index 636c0aefd8b..2f9a10a816d 100644
--- a/source/_posts/2016-09-10-notify-group-reload-api-pihole.markdown
+++ b/source/_posts/2016-09-10-notify-group-reload-api-pihole.markdown
@@ -30,7 +30,7 @@ There are countless bugfixes included in this release which will make your exper
The [Home Assistant API Documentation](https://dev-docs.home-assistant.io/en/dev/) is a great addition to the already existing user documentation. The focus is not end-users but developers who want to get details about the code without actually browsing the code on Github.
### Configuration validation
-The validation of the configuration is still on-going. Approximately 80 % is done. This means that we will propably talk about this topic in the next release notes again. To align the configuration of components and platforms we needed to break some. Please refer to the Breaking changes section to check if you need to update your configuration or simple check your log for configuration validation errors. Thanks to [@kellerza], [@fabaff], [@Teagan42], and [@pvizeli] for your effort!
+The validation of the configuration is still on-going. Approximately 80 % is done. This means that we will propably talk about this topic in the next release notes again. To align the configuration of components and platforms we needed to break some. Please refer to the Backward-incompatible changes section to check if you need to update your configuration or simple check your log for configuration validation errors. Thanks to [@kellerza], [@fabaff], [@Teagan42], and [@pvizeli] for your effort!
### All changes
@@ -87,7 +87,7 @@ The validation of the configuration is still on-going. Approximately 80 % is don
- Allow changing covers using scenes ([@nvella])
- Device tracker - Automatic: Fix polling ([@teagan42])
-### Breaking changes
+### Backward-incompatible changes
- [OpenweatherMap] entity IDs are now like `sensor.owm_temperature`. Previously they were like `sensor.weather_temperature`. Apologies for this change, but we needed to make OpenWeatherMap more generic now that we have many weather platforms.
- Updates of configuration variables due to configuration check or alignment with other platforms. Please update your configuration entries according to the documentation:
diff --git a/source/_posts/2016-09-29-async-sleepiq-emoncms-stocks.markdown b/source/_posts/2016-09-29-async-sleepiq-emoncms-stocks.markdown
index ef115522a8b..4c775aa5db7 100644
--- a/source/_posts/2016-09-29-async-sleepiq-emoncms-stocks.markdown
+++ b/source/_posts/2016-09-29-async-sleepiq-emoncms-stocks.markdown
@@ -22,7 +22,7 @@ There now is support for two new super cool things: Beds and license plates. [@t
### Configuration validation
-On the voluptuous front we have also made great progress. We were able to fully remove the legacy config helpers and have migrated 323 of the 346 components and platforms that needed migrating! This does mean that for some components the configuration has slightly changed, make sure to check out the breaking changes section at the bottom for more info. Thanks everybody for reviewing the Pull requests, testing the changes, and reporting issues.
+On the voluptuous front we have also made great progress. We were able to fully remove the legacy config helpers and have migrated 323 of the 346 components and platforms that needed migrating! This does mean that for some components the configuration has slightly changed, make sure to check out the backward-incompatible changes section at the bottom for more info. Thanks everybody for reviewing the Pull requests, testing the changes, and reporting issues.
### Delayed Release
@@ -100,7 +100,7 @@ Since 0.28 [automation rules](/blog/2016/09/10/notify-group-reload-api-pihole/#r
- Fix handling SIGTERM and SIGHUP signals (fixes Systemd restart issues) ([@pvizeli])
-### Breaking changes
+### Backward-incompatible changes
- The template methods `now` and `utcnow` have been changed from variables to methods. To get the current time replace `now` with `now()`.
- `yahooweather` default name is now `yweather`. Also min and max temperature are now correctly called `Temperature Min` and `Temperature Max`.
diff --git a/source/_posts/2016-10-08-hassbian-rest-digital-ocean.markdown b/source/_posts/2016-10-08-hassbian-rest-digital-ocean.markdown
index 877dd431139..7efa10f7fb9 100644
--- a/source/_posts/2016-10-08-hassbian-rest-digital-ocean.markdown
+++ b/source/_posts/2016-10-08-hassbian-rest-digital-ocean.markdown
@@ -40,7 +40,7 @@ As the results are processed on-the-fly you still need to use the data from your
### REST! We don't...
-There was a lot of work done on our implementation which are working with RESTful APIs. [@w1ll1am23] extended the [aREST] platforms to display if an aREST unit is available or not. The aREST implementations are now covered by the configuration check as well. Please check the Breaking changes section for more details.
+There was a lot of work done on our implementation which are working with RESTful APIs. [@w1ll1am23] extended the [aREST] platforms to display if an aREST unit is available or not. The aREST implementations are now covered by the configuration check as well. Please check the Backward-incompatible changes section for more details.
The [REST sensor][rest-sensor] supports now HTTP authentication (basic and digest) and custom headers. This will allow you to access resources which are protected. This sample sensor will access GitHub and retrieve the latest release number while by-passing the rate limit for non-authenticated requests.
@@ -117,7 +117,7 @@ sensor
- Fix for Slack targets ([@fabaff])
- Fix for Pushover targets ([@Nixon506E])
-### Breaking changes
+### Backward-incompatible changes
- All deprecated condition options from `automation` have been removed (deprecated since May and have printed warnings to your console):
- `use_trigger_values` is gone. You have to copy your triggers to conditions and adjust for the correct config.
diff --git a/source/_posts/2016-10-22-flash-briefing-updater-hacktoberfest.markdown b/source/_posts/2016-10-22-flash-briefing-updater-hacktoberfest.markdown
index ebd3f2d1b18..222038bf868 100644
--- a/source/_posts/2016-10-22-flash-briefing-updater-hacktoberfest.markdown
+++ b/source/_posts/2016-10-22-flash-briefing-updater-hacktoberfest.markdown
@@ -200,7 +200,7 @@ This is super annoying, I know, especially since we had said in [0.12][zero-one-
- Fix a spelling problem on user-facing error ([@robbiet480])
- YAML includes will ignore dirs/files prefixed with . ([@lwis])
-## Breaking changes
+## Backward-incompatible changes
- The [HTTP] component now takes a different format for authenticating IPs
- Configuration format has changed for [Proximity]
diff --git a/source/_posts/2016-11-05-hacktoberfest-influxdb-weather.markdown b/source/_posts/2016-11-05-hacktoberfest-influxdb-weather.markdown
index 22ee28145b1..ba3027379bd 100644
--- a/source/_posts/2016-11-05-hacktoberfest-influxdb-weather.markdown
+++ b/source/_posts/2016-11-05-hacktoberfest-influxdb-weather.markdown
@@ -108,7 +108,7 @@ Our website has now an additional category called "Ecosystem". This will become
- [iOS](/ecosystem/ios/)
- SceneGen
-### Breaking changes
+### Backward-incompatible changes
- The Yahoo Finance platform supports now multiple stock. Please adjust your configuration.
- Deprecated components `garage_door`, `rollershutter`, `thermostat`, and `hvac` have been removed.
diff --git a/source/_posts/2016-11-20-calendar--wink-thermostats--cisco-ios.markdown b/source/_posts/2016-11-20-calendar--wink-thermostats--cisco-ios.markdown
index f91a8ac7438..a8afe6a8226 100644
--- a/source/_posts/2016-11-20-calendar--wink-thermostats--cisco-ios.markdown
+++ b/source/_posts/2016-11-20-calendar--wink-thermostats--cisco-ios.markdown
@@ -64,7 +64,7 @@ But a new release wouldn't be awesome if it didn't had some new goodies and this
This should fix occasional performance problems that some people have reported.
-### Breaking changes
+### Backward-incompatible changes
- We have included a fix that impacts how we generate entity ids. This only impacts devices with accented characters. Instead of being stripped out, they are now replaced with the non-accented version. So now `Tèst Mörê` will become `test_more` instead of `tst_mr`.
- Command line switches will now use the specified object ID for their entity ID instead of basing it off the name.
diff --git a/source/_posts/2016-12-03-remote-websockets-sonarr.markdown b/source/_posts/2016-12-03-remote-websockets-sonarr.markdown
index 6fbf5663fec..1eb4a4269d2 100644
--- a/source/_posts/2016-12-03-remote-websockets-sonarr.markdown
+++ b/source/_posts/2016-12-03-remote-websockets-sonarr.markdown
@@ -127,7 +127,7 @@ We are working on a better solution for 0.35.
- Fix Nest cameras without activity zones ([@technicalpickles])
- Fix Plex doing I/O inside event loop ([@balloob])
-### Breaking changes
+### Backward-incompatible changes
- The [HomeMatic][homematic] component now uses a different syntax for hosts and the `set_value` service has been renamed.
- All [RFXtrx][rfxtrx] sensors will get a new entity ID.
diff --git a/source/_posts/2017-01-14-iss-usps-images-packages.markdown b/source/_posts/2017-01-14-iss-usps-images-packages.markdown
index 334acc223bf..f05bf240cd0 100644
--- a/source/_posts/2017-01-14-iss-usps-images-packages.markdown
+++ b/source/_posts/2017-01-14-iss-usps-images-packages.markdown
@@ -85,7 +85,7 @@ The new [image processing component][image] currently works with [number plates]
- Fix Bluetooth and Volvo trackers ([@pvizeli])
- Fix lannouncer notify platform ([@mKeRix])
-### Breaking changes
+### Backward-incompatible changes
- [APNS][apns] service was moved to the `notify` domain. Use `notify.apns_NOTIFIER_NAME` instead of `apns.NOTIFIER_NAME`.
- [InfluxDB][influx] component has a new [schema](/integrations/influxdb/#data-migration) to store values in the InfluxDB database. You may require to run the [`influxdb_migrator`](/integrations/influxdb/#migration-script) script.
diff --git a/source/_posts/2017-01-28-face-coffee-wink.markdown b/source/_posts/2017-01-28-face-coffee-wink.markdown
index 82f48cf4ccd..51e37497ad2 100644
--- a/source/_posts/2017-01-28-face-coffee-wink.markdown
+++ b/source/_posts/2017-01-28-face-coffee-wink.markdown
@@ -12,7 +12,7 @@ og_image: /images/blog/2017-01-0.37/social.png
---
-No stats, no numbers, and alike this time. Ok, just one number: 0.37. We are back on track with our bi-weekly release cycle. Beside some organizational changes is this release shipping again cool features and new integrations. Please keep an eye on the "Breaking changes" section because there are also massive improvements for some platforms and components.
+No stats, no numbers, and alike this time. Ok, just one number: 0.37. We are back on track with our bi-weekly release cycle. Beside some organizational changes is this release shipping again cool features and new integrations. Please keep an eye on the "Backward-incompatible changes" section because there are also massive improvements for some platforms and components.
### Governance
As announced, the new [Governance][gov] requires for developers to sign the CLA. [Code of Conduct][coc], [Contributor License Agreement][cla], and proper [Licensing][license] will to protect all involved parties in the Home Assistant eco-system from users and community members to contributors.
@@ -144,7 +144,7 @@ Bugfix: [@balloob], [@fabaff], [@freol35241], [@pvizeli], [@Danielhiversen], [@t
- Prevent infinite loop in crossconfigured mqtt event streams ([@aequitas])
- Fix Hue lightgroups failing on startup (@tboyce1)
-### Breaking changes
+### Backward-incompatible changes
- A **major** breaking change in the [`emulated_hue`][emul-hue] component means that unless you set `type: alexa` before starting up the newer Home Assistant version you will lose all devices that Alexa has discovered and will need to re-add them as well as create new groups.
- The platform of the [ISS][iss] integration was change to `binary_sensor`. Please check the platform documentation.
- The [Roku][roku] media uses now a new format for the entity IDs.
diff --git a/source/_posts/2017-02-11-alert-appletv-mqtt-yeelight.markdown b/source/_posts/2017-02-11-alert-appletv-mqtt-yeelight.markdown
index c16f604155f..80515377bea 100644
--- a/source/_posts/2017-02-11-alert-appletv-mqtt-yeelight.markdown
+++ b/source/_posts/2017-02-11-alert-appletv-mqtt-yeelight.markdown
@@ -131,7 +131,7 @@ Bugfixes: [@balloob], [@fabaff], [@pvizeli], [@mnoorenberghe] [@Danielhiversen],
- Hidden devices are no longer visible on views ([@balloob])
-### Breaking changes
+### Backward-incompatible changes
- The support for [LG webOS Smart TVs][webostv] was improved. This requires you to move `$HOME/.pylgtv` to `$HASS_CONFIG_DIR/webostv.conf` or Home Assistant will need to be paired with the TV again.
- Image processing events have been renamed: `identify_face` has become `image_processing.detect_face`, `found_plate` has become `image_processing.found_plate`
- The [FFmpeg binary sensor][ffmpeg-bin] change the platform name from `ffmpeg` to `ffmpeg_noise` and `ffmpeg_motion`. Also all FFmpeg-related services are moved from a platform implementation to a the [FFmpeg components][ffmpeg] and were rename from `binary_sensor.ffmpeg_xy` to `ffmpeg.xy`.
diff --git a/source/_posts/2017-02-25-config-panel-and-state-restoration.markdown b/source/_posts/2017-02-25-config-panel-and-state-restoration.markdown
index de06529836d..24dfbdad6e0 100644
--- a/source/_posts/2017-02-25-config-panel-and-state-restoration.markdown
+++ b/source/_posts/2017-02-25-config-panel-and-state-restoration.markdown
@@ -61,13 +61,13 @@ Thanks to [Fabian][@fabaff] we have a great re-organized documentation. Is it pe
Ever have some input components or integrations and get annoyed with the fact that their state is lost after a restart? Don't worry any longer. [Johann][@kellerza] has added the foundation for state restoration to Home Assistant. For the initial release support has been added to `input_select` and `input_boolean` components. We will be adding this to more integrations in the future.
-## Breaking changes to customize and Z-Wave "customize"
+## Backward-incompatible changes to customize and Z-Wave "customize"
A couple of releases ago we introduced a new way of doing `customize`. It became a list that allowed different ways of matching the config to the entity.
We realized that this was leading into a rabbit hole that we had to get out off. Besides making it unnecessarily complicated it also blocked the road to config panels. And who doesn't like config panels?
-So starting this release, we had to make some breaking changes to right the wrong. We will be releasing an online tool to help you convert your config to the new format later today.
+So starting this release, we had to make some backward-incompatible changes to right the wrong. We will be releasing an online tool to help you convert your config to the new format later today.
[**Update: the online tool can be found here.**](https://jsfiddle.net/balloob/d2e56q6f/74/)
@@ -207,7 +207,7 @@ And a final shout out to [Pascal][@pvizeli]. He keeps improving the performance
- Prevent discovered services and devices to be handled twice (@colinodell)
-#### Breaking changes
+#### Backward-incompatible changes
- VolvoOnCall has been extended with more features and had to be converted to a component
- Limitlessled support for Bridge v6 and RGBWW bulbs require users to specify `version` and `port
diff --git a/source/_posts/2017-03-11-repurpose-any-android-phone-as-ip-camera.markdown b/source/_posts/2017-03-11-repurpose-any-android-phone-as-ip-camera.markdown
index 775cb18dd4a..1edcaf9bc96 100644
--- a/source/_posts/2017-03-11-repurpose-any-android-phone-as-ip-camera.markdown
+++ b/source/_posts/2017-03-11-repurpose-any-android-phone-as-ip-camera.markdown
@@ -50,7 +50,7 @@ Screenshot of all the different functionality the IP webcam integration offers.
- Blink Home Security Camera support added ([@fronzbot])
- AppleTV has been converted to push data to Home Assistant instead of us having to poll ([@postlund])
-## Breaking changes
+## Backward-incompatible changes
- Vera entity ids have changed. This is a one time change to migrate to a model that will prevent future conflicts.
- The Twilio notify platforms now have to be configured via the twilio component.
diff --git a/source/_posts/2017-03-25-todo-volumio-workday.markdown b/source/_posts/2017-03-25-todo-volumio-workday.markdown
index 0db2868983d..dbdfb25429b 100644
--- a/source/_posts/2017-03-25-todo-volumio-workday.markdown
+++ b/source/_posts/2017-03-25-todo-volumio-workday.markdown
@@ -28,7 +28,7 @@ The new format of the changelog which was introduced with 0.40 will provide a li
- [Volumio][volumio] media player added ([@jslove])
- [Workday][workday] sensor ([@BastianPoe])
-## Breaking changes
+## Backward-incompatible changes
- The [Kodi notifier][kodi] platform was migrated to async and the configuration synced with the Kodi media player platform ([#6497]).
- For the [Music Player Daemon][mpd] (MPD) platform was `location` replaced with `name` ([#6553]).
diff --git a/source/_posts/2017-04-08-eddystone-beacons--lockitron-locks--total-connect.markdown b/source/_posts/2017-04-08-eddystone-beacons--lockitron-locks--total-connect.markdown
index 5d4cacfbbd2..4605bbf2248 100644
--- a/source/_posts/2017-04-08-eddystone-beacons--lockitron-locks--total-connect.markdown
+++ b/source/_posts/2017-04-08-eddystone-beacons--lockitron-locks--total-connect.markdown
@@ -34,7 +34,7 @@ Also want to take a moment to thank Austin Andrews aka [Templarian] for his [Mat
- The Ring doorbell has been integrated further with the inclusion of binary sensors ([@tchellomello] - [#6520])
-## Breaking changes
+## Backward-incompatible changes
- We were incorrectly treating groups named `default_view` as default views. Make sure you set `view: true` in the config for these groups. [#251 (frontend)](https://github.com/home-assistant/home-assistant-polymer/pull/251)
- The last release introduced a revamped LIFX platform. We only realized after deploy that this version does not work on Windows. We have added the old LIFX implementation back as `lifx_legacy`.
diff --git a/source/_posts/2017-04-22-ikea-tradfri--spotify.markdown b/source/_posts/2017-04-22-ikea-tradfri--spotify.markdown
index b138a700429..bbe0367fe74 100644
--- a/source/_posts/2017-04-22-ikea-tradfri--spotify.markdown
+++ b/source/_posts/2017-04-22-ikea-tradfri--spotify.markdown
@@ -49,7 +49,7 @@ Also note that you have till the end of the weekend to [submit an application][a
- myStrom Wifi Bulbs ([@fabaff] - [#7161]) ([light.mystrom docs]) (new-platform)
-## Breaking changes
+## Backward-incompatible changes
- Remove deprecated classes from `homeassistant.remote` ([@balloob] - [#7011])
- min_max sensor has a different default name and will ignore states that are unknown ([@micw] - [#6786])
diff --git a/source/_posts/2017-05-06-zigbee-opencv-dlib.markdown b/source/_posts/2017-05-06-zigbee-opencv-dlib.markdown
index 1a993fe3ab8..f4494996a64 100644
--- a/source/_posts/2017-05-06-zigbee-opencv-dlib.markdown
+++ b/source/_posts/2017-05-06-zigbee-opencv-dlib.markdown
@@ -60,7 +60,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
- MQTT Cover: Fixed status reporting for range with non-zero base ([@cribbstechnologies])
-## Breaking changes
+## Backward-incompatible changes
- Python Open Z-Wave made a release that fixed string processing. This was backwards incompatible. We have updated our code so you'll have to update to the latest Python Open Z-Wave with this release. You can also wait one release, as next release we'll introduce automatic installing of Python Open Z-Wave. ([@keatontaylor] - [#7266]) ([climate.zwave docs]) (breaking change)
- InfluxDB configuration to blacklist domains has been updated to allow more features. ([@janLo] - [#7264]) (breaking change)
diff --git a/source/_posts/2017-05-20-automation-editor-zwave-panel-ocr.markdown b/source/_posts/2017-05-20-automation-editor-zwave-panel-ocr.markdown
index b4ff294ea2c..1a6d7b85b81 100644
--- a/source/_posts/2017-05-20-automation-editor-zwave-panel-ocr.markdown
+++ b/source/_posts/2017-05-20-automation-editor-zwave-panel-ocr.markdown
@@ -85,7 +85,7 @@ If you are using our [experimental Hass.io image][hass.io], we made a breaking c
## Reporting Issues
Experiencing issues introduced by this release? Please report them in our [issue tracker][issue]. Make sure to fill in all fields of the issue template.
-## Breaking changes
+## Backward-incompatible changes
- PyPI Openzwave ([@JshWright] - [#7415]) ([zwave docs]) (breaking change)
- Remove listening to `homeassistant_start` with event automation ([@balloob] - [#7474]) ([automation.event docs]) (breaking change)
diff --git a/source/_posts/2017-06-04-release-46.markdown b/source/_posts/2017-06-04-release-46.markdown
index d85a067dde1..88c2ec3ace3 100644
--- a/source/_posts/2017-06-04-release-46.markdown
+++ b/source/_posts/2017-06-04-release-46.markdown
@@ -32,7 +32,7 @@ It's time for 0.46! This release does not have too many new integrations, instea
- Sensor - MetOffice: Fix last updated date ([@cyberjacob] - [#7965]) ([metoffice docs])
- Prevent Roku doing I/O in event loop ([@balloob] - [#7969]) ([media_player.roku docs])
-## Breaking changes
+## Backward-incompatible changes
- The USPS sensor entity names have changed as there are now two. One for packages and one for mail. Config will now also use `scan_interval` instead of `update_interval` ([@happyleavesaoc] - [#7655]) (breaking change)
- Automation state trigger: From/to checks will now ignore state changes that are just attribute changess ([@amelchio] - [#7651]) ([automation.state docs]) (breaking change)
diff --git a/source/_posts/2017-06-15-zwave-entity-ids.markdown b/source/_posts/2017-06-15-zwave-entity-ids.markdown
index 740a82a1083..94765c1344f 100644
--- a/source/_posts/2017-06-15-zwave-entity-ids.markdown
+++ b/source/_posts/2017-06-15-zwave-entity-ids.markdown
@@ -15,6 +15,6 @@ Now that users are able to control these names, we will be making changes to how
With the release of 0.47, this feature will be opt-in. Setting `new_entity_ids: true` under `zwave:` in your configuration.yaml will enable the new generation. After 0.48 this feature will become opt-out. From 0.48 onward, unless you’ve declared `new_entity_ids: false` you will switch to the new entity_id generation. At an undecided point in the future, the old entity_id generation will be removed completely.
-I’m sure all ZWave users understand that the current entity_ids aren’t easy to use. They’re annoying to type in configuration.yaml, and break if a node needs to be re-included to the network. We know that breaking changes are painful, and so we’re doing what we can to roll this change out as smoothly as possible. The end result should be a dramatic simplification of most ZWave configurations. We hope that this change will ultimately make ZWave much easier to work with, and bring ZWave configuration just a little closer to the rest of the Home Assistant platforms.
+I’m sure all ZWave users understand that the current entity_ids aren’t easy to use. They’re annoying to type in configuration.yaml, and break if a node needs to be re-included to the network. We know that backward-incompatible changes are painful, and so we’re doing what we can to roll this change out as smoothly as possible. The end result should be a dramatic simplification of most ZWave configurations. We hope that this change will ultimately make ZWave much easier to work with, and bring ZWave configuration just a little closer to the rest of the Home Assistant platforms.
[@turbokongen]: https://github.com/turbokongen
diff --git a/source/_posts/2017-06-17-release-47.markdown b/source/_posts/2017-06-17-release-47.markdown
index 739b2ae7f7e..fd878d17000 100644
--- a/source/_posts/2017-06-17-release-47.markdown
+++ b/source/_posts/2017-06-17-release-47.markdown
@@ -91,7 +91,7 @@ To run without the monkey patch, start Home Assistant with `HASS_NO_MONKEY=1 has
Experiencing issues introduced by this release? Please report them in our [issue tracker][issue]. Make sure to fill in all fields of the issue template.
-## Breaking changes
+## Backward-incompatible changes
- Update opencv config to match other image processors ([@Teagan42] - [#7864]) ([image_processing.opencv docs]) (breaking change)
diff --git a/source/_posts/2017-07-02-release-48.markdown b/source/_posts/2017-07-02-release-48.markdown
index 44269d43f68..f7172896c64 100644
--- a/source/_posts/2017-07-02-release-48.markdown
+++ b/source/_posts/2017-07-02-release-48.markdown
@@ -75,7 +75,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
-## Breaking Changes
+## Backward-incompatible changes
- We have added a new option to whitelist folders that can be used as sources for sending files. You will need to use this option if you are using files with the telegram component. ([@pvizeli] - [#8189]) (breaking change)
diff --git a/source/_posts/2017-07-16-release-49.markdown b/source/_posts/2017-07-16-release-49.markdown
index b8d8ae6c28c..9e8977ff526 100644
--- a/source/_posts/2017-07-16-release-49.markdown
+++ b/source/_posts/2017-07-16-release-49.markdown
@@ -83,7 +83,7 @@ This feature has also been brought to you by [@Andrey-git]! Big shout out to him
Experiencing issues introduced by this release? Please report them in our [issue tracker][issue]. Make sure to fill in all fields of the issue template.
-## Breaking Changes
+## Backward-incompatible changes
- UPC Connect component no longer needs a password passed into the configuration. ([@Flavien] - [#8335]) ([device_tracker.upc_connect docs]) (breaking change)
- The Apple TV platform has been upgraded to a component and a remote platform has been added. This requires your Apple TV configuration to be moved to the new `apple_tv` component. ([@postlund] - [#8122]) ([media_player.apple_tv docs]) (breaking change)
diff --git a/source/_posts/2017-07-29-release-50.markdown b/source/_posts/2017-07-29-release-50.markdown
index 9a9c8125d26..76fa9788b91 100644
--- a/source/_posts/2017-07-29-release-50.markdown
+++ b/source/_posts/2017-07-29-release-50.markdown
@@ -89,7 +89,7 @@ Straight to 0.50.2. We released 0.50 as 0.50.1 due to an upload error to PyPi.
Experiencing issues introduced by this release? Please report them in our [issue tracker][issue]. Make sure to fill in all fields of the issue template.
-## Breaking Changes
+## Backward-incompatible changes
- Automations: The state trigger keyword `state` and the time trigger keyword `after` were deprecated in 0.46. They have now been removed. Use `to` and `at` instead. ([@amelchio] - [#8510]) ([automation.state docs]) ([automation.time docs]) (breaking change)
- Wink: the component is no longer supporting the `access_token` in the config. Use the new OAuth authentication or add your username and password to the config. ([@w1ll1am23] - [#8208]) ([wink docs]) (breaking change)
diff --git a/source/_posts/2017-08-12-release-51.markdown b/source/_posts/2017-08-12-release-51.markdown
index d970b4d8232..699d239dede 100644
--- a/source/_posts/2017-08-12-release-51.markdown
+++ b/source/_posts/2017-08-12-release-51.markdown
@@ -80,7 +80,7 @@ As we have seen more vacuum cleaners land in Home Assistant, it was time to crea
Experiencing issues introduced by this release? Please report them in our [issue tracker][issue]. Make sure to fill in all fields of the issue template.
-## Breaking Changes
+## Backward-incompatible changes
- Efergy sensors: change units from KW to W ([@emlt] - [#8761]) ([sensor.efergy docs]) (breaking change)
- Xiaomi vacuum is now a platform of new `vacuum` component derived from ToggleEntity, and services ([@azogue] - [#8623]) (breaking change) (new-platform)
diff --git a/source/_posts/2017-08-26-release-0-52.markdown b/source/_posts/2017-08-26-release-0-52.markdown
index e9f434c746b..ab41a7e1058 100644
--- a/source/_posts/2017-08-26-release-0-52.markdown
+++ b/source/_posts/2017-08-26-release-0-52.markdown
@@ -66,7 +66,7 @@ script: !include scripts.yaml
Experiencing issues introduced by this release? Please report them in our [issue tracker][issue]. Make sure to fill in all fields of the issue template.
-## Breaking Changes
+## Backward-incompatible changes
- Remove spaces from Xiami switch attributes ([@syssi] - [#8952]) ([switch.xiaomi docs]) (breaking change)
- MQTT Switch: command and availability payload are now no longer linked. Command and availability payload default to ON/OFF and must be configured individually if custom values are required. ([@timstanley1985] - [#8934]) ([switch.mqtt docs]) (breaking change)
diff --git a/source/_posts/2017-09-09-release-53.markdown b/source/_posts/2017-09-09-release-53.markdown
index 1386f2fc92a..1bed70cb95d 100644
--- a/source/_posts/2017-09-09-release-53.markdown
+++ b/source/_posts/2017-09-09-release-53.markdown
@@ -87,7 +87,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
-## Breaking Changes
+## Backward-incompatible changes
- The new customize editor is using the file `customize.yaml` in your config folder. If you are using this file today for other config, make sure to rename it before using the new customize UI editor. ([@andrey-git] - [#9134]) ([config docs]) (breaking change) (new-platform)
- The frontend component now supports loading custom html files when Home Assistant front end starts ([@andrey-git] - [#9150]) (breaking change). It could be Javascript, CSS or custom Web Components. Along there was a breaking change in the way Custom UI is used:
diff --git a/source/_posts/2017-09-23-release-54.markdown b/source/_posts/2017-09-23-release-54.markdown
index 350360dde36..1176fe1dbbc 100644
--- a/source/_posts/2017-09-23-release-54.markdown
+++ b/source/_posts/2017-09-23-release-54.markdown
@@ -39,7 +39,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
-## Breaking Changes
+## Backward-incompatible changes
- Sensor - OneWire: This update changes the names of the sensors from `-## Noteworthy breaking changes +## Noteworthy backward-incompatible changes For the last couple of releases, we've been printing warnings if your configuration contained invalid slugs or extra keys. Starting with this release, these warnings are now errors. No procrastination anymore, you'll need to fix it now. @@ -167,7 +167,7 @@ Experiencing issues introduced by this release? Please report them in our [issue -## Breaking Changes +## Backward-incompatible changes - No longer allow invalid slugs or extra keys ([@balloob] - [#24176]) (breaking change) - Add service for adding event to google component ([@isabellaalstrom] - [#22473]) ([google docs]) (breaking change) diff --git a/source/_posts/2019-07-17-release-96.markdown b/source/_posts/2019-07-17-release-96.markdown index e51d050a1c9..711b3669d03 100644 --- a/source/_posts/2019-07-17-release-96.markdown +++ b/source/_posts/2019-07-17-release-96.markdown @@ -272,7 +272,7 @@ Experiencing issues introduced by this release? Please report them in our [issue -## Breaking Changes +## Backward-incompatible changes - __OpenTherm__ - Adds support for more than one OpenTherm Gateway device which changes the configuration structure. ([@mvn23] - [#22932]) ([opentherm_gw docs]) diff --git a/source/_posts/2019-08-07-release-97.markdown b/source/_posts/2019-08-07-release-97.markdown index 212e1ed25d7..dbb27cc06c9 100644 --- a/source/_posts/2019-08-07-release-97.markdown +++ b/source/_posts/2019-08-07-release-97.markdown @@ -145,7 +145,7 @@ Experiencing issues introduced by this release? Please report them in our [issue -## Breaking Changes +## Backward-incompatible changes - **Python** - Bump Python support to min Python 3.6.0 ([@balloob] - [#25582]) - **Z-Wave** - Improve handling of Z-Wave config entry vs yaml config. If a Z-Wave `network_key` is specified in configuration.yaml it will override a `network_key` specified in the Z-Wave config entry. ([@cgarwood] - [#25112]) ([zwave docs]) diff --git a/source/_posts/2019-08-28-release-98.markdown b/source/_posts/2019-08-28-release-98.markdown index 410fce47315..f88ad47bdfb 100644 --- a/source/_posts/2019-08-28-release-98.markdown +++ b/source/_posts/2019-08-28-release-98.markdown @@ -38,7 +38,7 @@ Screenshot of integration system options ## Config Entry Options -We introduced config entries last year as our way as a generic way for integrations to store authentication and configuration. By allowing integrations to define the storage format, there are no more breaking changes for anything stored inside config entries! +We introduced config entries last year as our way as a generic way for integrations to store authentication and configuration. By allowing integrations to define the storage format, there are no more backward-incompatible changes for anything stored inside config entries! Config entries also work great with people who prefer configuration.yaml. At startup a config entry is created/updated with the configuration. @@ -215,7 +215,7 @@ Experiencing issues introduced by this release? Please report them in our [issue -## Breaking Changes +## Backward-incompatible changes - **Deprecated** diff --git a/source/_posts/2019-09-18-release-99.markdown b/source/_posts/2019-09-18-release-99.markdown index b623adfd537..bc0d80edda7 100644 --- a/source/_posts/2019-09-18-release-99.markdown +++ b/source/_posts/2019-09-18-release-99.markdown @@ -116,7 +116,7 @@ We also had some great drinks in the evenings with companies that integrate with [@timmo] has released version 2.0 of his Home Panel. This is an alternative user interface for Home Assistant. -Released `v3.7.95` to NPM/CDN. 100 new icons! 🧙♂️ Preview: https://t.co/N02X3rnQ8N Read more: https://t.co/CHQ3TEdVM2 #MaterialDesign #OpenSource pic.twitter.com/LlWy8RfFVu
— Material Icons (@MaterialIcons) June 22, 2019
It's finally here. 🎉
— Timmo (@timmo001) September 14, 2019 +
Home Panel v2.0.0 is now released and has been completely rewritten in #React with #TypeScript
⚠️Please read the release notes before upgrading as are breaking changes to know about before upgrading!https://t.co/NMDQu4zZW8#HomePanel #HomeAssistant pic.twitter.com/ucA1HxwurB[@cogneato]: https://github.com/cogneato @@ -191,7 +191,7 @@ Experiencing issues introduced by this release? Please report them in our [issue -## Breaking Changes +## Backward-incompatible changes - **Unifi** - Removes support of directly configuring the UniFi platform for device trackers. Use `unifi:` instead. Extra configuration through config entry options from the GUI (see release notes 0.98 for example) and through unifi configuration in configuration.yaml will continue to work.- ([@Kane610] - [#26587]) ([unifi docs]) diff --git a/source/_posts/2019-10-10-release-100.markdown b/source/_posts/2019-10-10-release-100.markdown index d090b5c9f92..547522673d7 100644 --- a/source/_posts/2019-10-10-release-100.markdown +++ b/source/_posts/2019-10-10-release-100.markdown @@ -196,7 +196,7 @@ Experiencing issues introduced by this release? Please report them in our [issue -## Breaking Changes +## Backward-incompatible changes - **Removed** - The following integrations which were marked in .98 for pending removal have now been removed (ADR-0004): - **UPS** - ([@frenck] - [#26824]) diff --git a/source/_posts/2019-10-30-release-101.markdown b/source/_posts/2019-10-30-release-101.markdown index 9c16373a7f7..8847cf619d9 100644 --- a/source/_posts/2019-10-30-release-101.markdown +++ b/source/_posts/2019-10-30-release-101.markdown @@ -220,7 +220,7 @@ Experiencing issues introduced by this release? Please report them in our [issue -## Breaking Changes +## Backward-incompatible changes - __Removed__ - The following integrations have been removed: - __Direct authentication via trusted networks or API password__ - It is no longer possible to make authenticated requests using trusted networks or by appending ?api_password=X to the URL. You will now first need to get an authentication token and use that token to make requests. Auth providers for trusted networks and API passwords are still available. - ([@balloob] - [#27656]) ([auth docs]) ([http docs]) ([websocket_api docs]) diff --git a/source/_posts/2019-11-20-release-102.markdown b/source/_posts/2019-11-20-release-102.markdown index a5b3a656fd9..b758b513953 100644 --- a/source/_posts/2019-11-20-release-102.markdown +++ b/source/_posts/2019-11-20-release-102.markdown @@ -134,7 +134,7 @@ Users of Xiaomi Vacuum cleaners can now use this great custom Lovelace card: Experiencing issues introduced by this release? Please report them in our [issue tracker](https://github.com/home-assistant/home-assistant/issues). Make sure to fill in all fields of the issue template. -## Breaking Changes +## Backward-incompatible changes - **Huawei LTE** - Configuration has been consolidated below `huawei_lte`. Device tracker no longer uses known_devices.yaml but entity registry. - ([@scop] - [#26675]) ([huawei_lte docs]) diff --git a/source/_posts/2019-12-11-release-103.markdown b/source/_posts/2019-12-11-release-103.markdown index cab03b97767..efb70428ab3 100644 --- a/source/_posts/2019-12-11-release-103.markdown +++ b/source/_posts/2019-12-11-release-103.markdown @@ -176,7 +176,7 @@ The following platforms have been added to existing integrations: - Add Huawei LTE binary sensor support, mobile connection sensor ([@scop] - [#28226]) ([huawei_lte docs]) (new-platform) - Broadlink remote ([@felipediel] - [#26528]) ([broadlink docs]) (new-platform) -## Breaking Changes +## Backward-incompatible changes If you are an existing user, make sure to read the this section **before** upgrading, this helps you understand the changes and avoids having issues during an upgrade. @@ -217,7 +217,7 @@ All services for use in Home Assistant are moved to their integration naming spa - **Xiaomi Miio**: `*.xiaomi_*` -> `xiaomi_miio.*` ([#29134]) - **Yamaha**: `media_player.yamaha_*` -> `yamaha.*` ([#29142]) -### Other Breaking Changes +### Other backward-incompatible changes - **Mobile App** - Loading the Mobile App no longer causes the Cloud integration to be loaded. If you relied on this, add `cloud:` to your configuration.yaml. - ([@balloob] - [#29373]) ([mobile_app docs]) - **Samsung TV** - The behavior for next and previous track commands for Samsung TVs has changed. Before the change, the Samsung TV integration reacted to the two above commands sending the KEY_FF and KEY_REWIND commands. While watching TV programs, those two commands do nothing. After the change, the entity sends the KEY_CHUP and KEY_CHDOWN commands instead, thus allowing the user to change the channel using the media player standard Lovelace interface. The user doesn't need to change anything in the configuration. - ([@tulindo] - [#28213]) ([samsungtv docs]) diff --git a/source/_posts/2020-01-15-release-104.markdown b/source/_posts/2020-01-15-release-104.markdown index 93686e3b782..f155bb05138 100644 --- a/source/_posts/2020-01-15-release-104.markdown +++ b/source/_posts/2020-01-15-release-104.markdown @@ -29,7 +29,7 @@ We are starting this new year with a packed release! So let us dive in! - [In other news](/blog/2020/01/15/release-104/#in-other-news) - [New Integrations](/blog/2020/01/15/release-104/#new-integrations) - [New Platforms](/blog/2020/01/15/release-104/#new-platforms) -- [Breaking Changes](/blog/2020/01/15/release-104/#breaking-changes) +- [Backward-incompatible changes](/blog/2020/01/15/release-104/#backward-incompatible-changes) - [Beta Fixes](/blog/2020/01/15/release-104/#beta-fixes) - [All changes](/blog/2020/01/15/release-104/#all-changes) @@ -89,7 +89,7 @@ Furthermore, time to say bye-bye, to all generated entity groups (`group.all_*`). Chances are, you have never heard of those because they were hidden. However, if you rely on those groups for your automations, you need to adjust those automations. -Check out the [breaking changes section](#breaking-changes) for more information. +Check out the [backward-incompatible changes section](#backward-incompatible-changes) for more information. ## Add a device to Lovelace @@ -215,7 +215,7 @@ Make sure to fill in all fields of the issue template, that is helping us a lot! -## Breaking Changes +## Backward-incompatible changes - __Default groups__ - Entity integrations will no longer automatically maintain the hidden groups with all of their entities. The following groups are no longer automatically created and maintained: diff --git a/source/_posts/2020-02-05-release-105.markdown b/source/_posts/2020-02-05-release-105.markdown index 9e18d1b5fb3..d0e87c89c07 100644 --- a/source/_posts/2020-02-05-release-105.markdown +++ b/source/_posts/2020-02-05-release-105.markdown @@ -27,7 +27,7 @@ This means, it is now over a year ago that Lovelace was officially introduced as If you are not using Lovelace yet, we advise you to switch to it today. Lovelace is, by default, almost the same as old states UI with the bonus of a lot of flexibility, if you want it. -In addition to this, all configuration options for the States UI are deprecated as well. Please be sure to read the [breaking changes](#breaking-changes) to see if you have options that need to be removed from your configuration. +In addition to this, all configuration options for the States UI are deprecated as well. Please be sure to read the [backward-incompatible changes](#backward-incompatible-changes) to see if you have options that need to be removed from your configuration. ## Safe mode @@ -107,7 +107,7 @@ Screen recording of the zones editor. The new editor will only work for zones that are created in the UI, zones that are set up in `configuration.yaml` are read-only. -Additionally, if you define zones in your YAML configuration, please be aware that setting a [`name` is now required](#breaking-changes). +Additionally, if you define zones in your YAML configuration, please be aware that setting a [`name` is now required](#backward-incompatible-changes). As an extra added bonus, a new service was added: `zone.reload`. This service allows you to reload your zone configuration without restarting Home Assistant. @@ -184,7 +184,7 @@ Experiencing issues introduced by this release? Please report them in our [issue -## Breaking Changes +## Backward-incompatible changes - __Safe Mode__ - `--demo-mode` has been removed. A new safe mode has now been introduced, which loads the bare minimum necessary to load the Home Assistant frontend and allows for managing the configuration. This is not yet perfect. An invalid core configuration can still cause Home Assistant to refuse to start up. ([@balloob] - [#30723]) ([frontend docs]) ([http docs]) ([safe_mode docs]) diff --git a/source/_posts/2020-02-26-release-106.markdown b/source/_posts/2020-02-26-release-106.markdown index 907c36289c2..7c6a28de150 100644 --- a/source/_posts/2020-02-26-release-106.markdown +++ b/source/_posts/2020-02-26-release-106.markdown @@ -145,7 +145,7 @@ Experiencing issues introduced by this release? Please report them in our [issue -## Breaking Changes +## Backward-incompatible changes - **Tesla** - Tesla default scan interval has been raised to 660 seconds from 300 seconds. This is the result of new testing showing the prior default would not allow Tesla vehicles to fall asleep. You should reevaluate your scan interval if you have changed it, to avoid battery drain. The scan interval has had the minimum lowered to 60. - ([@alandtse] - [#31194]) ([tesla docs]) diff --git a/source/_posts/2020-03-18-release-107.markdown b/source/_posts/2020-03-18-release-107.markdown index 6d4e29abf94..d87303da76f 100644 --- a/source/_posts/2020-03-18-release-107.markdown +++ b/source/_posts/2020-03-18-release-107.markdown @@ -162,7 +162,7 @@ Experiencing issues introduced by this release? Please report them in our [issue -## Breaking Changes +## Backward-incompatible changes - **Xfinity Gateway** *(Deprecated)* - The Xfinity Gateway integration relies on web scraping and is deprecated, to be removed in Home Assistant Core 0.109. (ADR-0004) - ([@frenck] - [#32017]) diff --git a/source/_posts/2020-04-08-release-108.markdown b/source/_posts/2020-04-08-release-108.markdown index fa4f4c8a5d2..3dec2e93b26 100644 --- a/source/_posts/2020-04-08-release-108.markdown +++ b/source/_posts/2020-04-08-release-108.markdown @@ -201,7 +201,7 @@ Experiencing issues introduced by this release? Please report them in our [issue -## Breaking Changes +## Backward-incompatible changes - **Lovelace themes** - We discovered our theme logic was wrong, when you didn't specify a theme for a Lovelace card or view. It would default to the backend selected theme, even when your local theme was different, or your view had a different theme. To fix this we removed the options `default` and `Backend selected` from the Lovelace theme selection, and when there is not theme selected it will not set a theme. This will make sure the element has the same theme as its parent. diff --git a/source/_posts/2020-04-14-the-future-of-yaml.markdown b/source/_posts/2020-04-14-the-future-of-yaml.markdown index 588a354e1a5..f5689b82280 100644 --- a/source/_posts/2020-04-14-the-future-of-yaml.markdown +++ b/source/_posts/2020-04-14-the-future-of-yaml.markdown @@ -57,9 +57,9 @@ Goal: _**Making things easier.**_ The goal of making it easier is currently the main focus. -## Breaking changes +## Backward-incompatible changes -We all dislike them, those breaking changes when a new release is published. +We all dislike them, those backward-incompatible changes when a new release is published. We all scan the release notes hoping you are not affected by any of them in that release. @@ -129,7 +129,7 @@ maintenance and support burden. The amount of energy that needs to be put in understand and accept that. If we do not do that, a contributor could simply stop contributing. -Unfortunately, such a move creates breaking changes and often leads to a few +Unfortunately, such a move creates backward-incompatible changes and often leads to a few pretty de-motivating comments, towards the contributor and the project in general. This is harmful to everybody, as the contributors get demotivated or, even worse, don’t want to implement new features or create a breaking change. diff --git a/source/_posts/2020-04-29-release-109.markdown b/source/_posts/2020-04-29-release-109.markdown index 12f7c254802..44cd623f8bb 100644 --- a/source/_posts/2020-04-29-release-109.markdown +++ b/source/_posts/2020-04-29-release-109.markdown @@ -189,7 +189,7 @@ Experiencing issues introduced by this release? Please report them in our [issue -## Breaking Changes +## Backward-incompatible changes - **Flu Near You** - This integration is now available to be added from the UI. The `monitored_conditions` setting has been removed. You will need to diff --git a/source/_posts/2020-05-20-release-110.markdown b/source/_posts/2020-05-20-release-110.markdown index e608767b0ef..ab428079abc 100644 --- a/source/_posts/2020-05-20-release-110.markdown +++ b/source/_posts/2020-05-20-release-110.markdown @@ -299,7 +299,7 @@ you've enabled advanced mode on your user profile. happens, it will be prevented and write an error message to your log, similar to how the I/O detection does it (released in [0.109](/blog/2020/04/29/release-109/#detection-of-blocking-io-in-the-event-loop)). -- The ISY994 got a major upgrade! While it has quite a few breaking changes, it +- The ISY994 got a major upgrade! While it has quite a few backward-incompatible changes, it is now available via the UI and many bug are squashed. Thanks [@shbatm]! ## New Integrations @@ -353,7 +353,7 @@ Experiencing issues introduced by this release? Please report them in our [issue -## Breaking Changes +## Backward-incompatible changes - **Manual Alarm Panel** - When going from state `disarmed` to any other (armed) state such as `armed_away`, the state will be `arming` instead of `pending` during @@ -512,10 +512,10 @@ Experiencing issues introduced by this release? Please report them in our [issue significant update to the original module used to communicate with the ISY. ([@shbatm] - [#35212], [#35338], [#35413], [#35391] ) ([isy994 docs]) - As part of the update and many bug fixes, some breaking changes were introduced: + As part of the update and many bug fixes, some backward-incompatible changes were introduced:It's finally here. 🎉
— Timmo (@timmo001) September 14, 2019
Home Panel v2.0.0 is now released and has been completely rewritten in #React with #TypeScript
⚠️Please read the release notes before upgrading as are backward-incompatible changes to know about before upgrading!https://t.co/NMDQu4zZW8#HomePanel #HomeAssistant pic.twitter.com/ucA1HxwurB-Click see all breaking changes for ISY994
+Click see all backward-incompatible changes for ISY994
- Remove ISY Climate Module support: the ISY Climate Module was retired by UDI on 3/30/2020: UDI Announcement, support has been removed from the module, diff --git a/source/_posts/2020-06-10-release-111.markdown b/source/_posts/2020-06-10-release-111.markdown index 47185392745..1a44b073180 100644 --- a/source/_posts/2020-06-10-release-111.markdown +++ b/source/_posts/2020-06-10-release-111.markdown @@ -154,7 +154,7 @@ Experiencing issues introduced by this release? Please report them in our [issue -## Breaking Changes +## Backward-incompatible changes - **Frontend** diff --git a/source/_posts/2020-07-01-release-112.markdown b/source/_posts/2020-07-01-release-112.markdown index dd83010e610..37311c10488 100644 --- a/source/_posts/2020-07-01-release-112.markdown +++ b/source/_posts/2020-07-01-release-112.markdown @@ -288,7 +288,7 @@ Experiencing issues introduced by this release? Please report them in our [issue -## Breaking Changes +## Backward-incompatible changes - **Tile** @@ -322,7 +322,7 @@ Experiencing issues introduced by this release? Please report them in our [issue - **Xiaomi Miio** - Due to general code updates to the xiaomi_miio vacuum component there are breaking changes to the following services: + Due to general code updates to the xiaomi_miio vacuum component there are backward-incompatible changes to the following services: - `xiaomi_miio.vacuum_remote_control_start` - `xiaomi_miio.vacuum_remote_control_stop` @@ -514,7 +514,7 @@ Previously the `autobypass` configuration option only worked for `home` and `awa - **Hunter Hydrawise** - Hydrawise made an API change that removed rain sensor status, changed the behavior of the automatic watering switches, and the way in which the watering schedule is reported. As a result, the following breaking changes were made. + Hydrawise made an API change that removed rain sensor status, changed the behavior of the automatic watering switches, and the way in which the watering schedule is reported. As a result, the following backward-incompatible changes were made. - The rain sensor is no longer available. - The `auto_watering` switch state now reports `off` when the corresponding watering zone is actively watering. If `auto_watering` is enabled the switch status will report `off` when watering starts and will return to `on` when watering stops in that zone. diff --git a/source/_posts/2020-07-01-release-113.markdown b/source/_posts/2020-07-01-release-113.markdown index 39f4da2d98f..098cb7aa996 100644 --- a/source/_posts/2020-07-01-release-113.markdown +++ b/source/_posts/2020-07-01-release-113.markdown @@ -330,7 +330,7 @@ every 10 seconds. This is ideal for things like a doorbell. It has taken some time for us to upgrade to the newest version of [Material Design Icons][mdi], 5.3.45, there was a reason for that, -version [5.0.45][mdi-upgrade] contains a lot of breaking changes. +version [5.0.45][mdi-upgrade] contains a lot of backward-incompatible changes. We wanted to handle these well, so it took some time. @@ -444,7 +444,7 @@ Experiencing issues introduced by this release? Please report them in our [issue -## Breaking Changes +## Backward-incompatible changes Below is a listing of the breaking change for this release, per subject or integration. Click on one of those to read more about the breaking change diff --git a/source/_posts/2020-08-12-release-114.markdown b/source/_posts/2020-08-12-release-114.markdown index 321cb768781..d72e013ba52 100644 --- a/source/_posts/2020-08-12-release-114.markdown +++ b/source/_posts/2020-08-12-release-114.markdown @@ -231,7 +231,7 @@ Experiencing issues introduced by this release? Please report them in our [issue -## Breaking Changes +## Backward-incompatible changes Below is a listing of the breaking change for this release, per subject or integration. Click on one of those to read more about the breaking change diff --git a/source/_posts/2020-09-12-android-240-release.markdown b/source/_posts/2020-09-12-android-240-release.markdown index be03d5af208..0fa2c690766 100644 --- a/source/_posts/2020-09-12-android-240-release.markdown +++ b/source/_posts/2020-09-12-android-240-release.markdown @@ -13,7 +13,7 @@ og_image: /images/blog/2020-09-12-android-240-release/Companion.png Hey there, I hope everyone has been enjoying the last release of the Android app. We have another update coming up where we felt it's time to give everyone a heads up before release. There are several new changes done that you will immediately notice after installing the update to 2.4.0, so we wanted to cover what's new. You can expect this release to be available in the Google Play Store tomorrow. -## Current and Future Breaking Changes +## Current and Future Backward-incompatible changes Sometimes when we move really fast, we may move a bit too fast. While we had fun adding all the new sensors, we didn't stop to think about the new user experience and how we are making a burden on them by having non-static attributes for some of the sensors. In reality, these attributes are a state and we need to treat them as such. If we don't, there will be a need to use templates that are not user-friendly. We wanted to fix this issue and be courteous to our current users, so we have made a few changes. Some of which take place in this release and some in the following release after 2.4.0. diff --git a/source/_posts/2020-09-17-release-115.markdown b/source/_posts/2020-09-17-release-115.markdown index e3a011ea887..1ebe82b3838 100644 --- a/source/_posts/2020-09-17-release-115.markdown +++ b/source/_posts/2020-09-17-release-115.markdown @@ -104,7 +104,7 @@ navigating you around this release. - [New Platforms](#new-platforms) - [Integrations now available to set up from the UI](#integrations-now-available-to-set-up-from-the-ui) - [If you need help...](#if-you-need-help) -- [Breaking Changes](#breaking-changes) +- [Backward-incompatible changes](#backward-incompatible-changes) - [Farewell to the following](#farewell-to-the-following) - [Release 0.115.1 - September 18](#release-01151---september-18) - [Release 0.115.2 - September 19](#release-01152---september-19) @@ -879,7 +879,7 @@ Experiencing issues introduced by this release? Please report them in our [issue -## Breaking Changes +## Backward-incompatible changes Below is a listing of the breaking change for this release, per subject or integration. Click on one of those to read more about the breaking change diff --git a/source/_posts/2020-10-07-release-116.markdown b/source/_posts/2020-10-07-release-116.markdown index cbca00ad9d6..ff7467325ce 100644 --- a/source/_posts/2020-10-07-release-116.markdown +++ b/source/_posts/2020-10-07-release-116.markdown @@ -50,7 +50,7 @@ As always, enjoy the release! - [Release 0.116.3 - October 15](#release-01163---october-15) - [Release 0.116.4 - October 15](#release-01164---october-15) - [If you need help...](#if-you-need-help) -- [Breaking Changes](#breaking-changes) +- [Backward-incompatible changes](#backward-incompatible-changes) - [All changes](#all-changes) ## Entities card editor @@ -317,7 +317,7 @@ Experiencing issues introduced by this release? Please report them in our [issue -## Breaking Changes +## Backward-incompatible changes Below is a listing of the breaking change for this release, per subject or integration. Click on one of those to read more about the breaking change @@ -327,7 +327,7 @@ for that specific item.Custom Lovelace Cards
-This release contains breaking changes for custom card developers, check the +This release contains backward-incompatible changes for custom card developers, check the [developers blog](https://developers.home-assistant.io/blog/2020/10/02/lazyMoreInfo) for more information. diff --git a/source/_posts/2020-10-28-release-117.markdown b/source/_posts/2020-10-28-release-117.markdown index 4dc04c06bee..a361faa5820 100644 --- a/source/_posts/2020-10-28-release-117.markdown +++ b/source/_posts/2020-10-28-release-117.markdown @@ -64,7 +64,7 @@ So, keep an eye on our social media for the announcement. - [Release 0.117.5 - November 5](#release-01175---november-5) - [Release 0.117.6 - November 11](#release-01176---november-11) - [If you need help...](#if-you-need-help) -- [Breaking Changes](#breaking-changes) +- [Backward-incompatible changes](#backward-incompatible-changes) - [Farewell to the following](#farewell-to-the-following) - [All changes](#all-changes) @@ -231,7 +231,7 @@ more advanced future additions and can significantly reduce the complexity of existing templates in your set up. It should be mostly compatible with your existing templates, however, if you -enable this feature, please be sure to check the breaking changes section. +enable this feature, please be sure to check the backward-incompatible changes section. We'd love to hear you experience with using this feature! And, if you run into, problems, [please let us know][problem]. @@ -511,7 +511,7 @@ Experiencing issues introduced by this release? Please report them in our [issue -## Breaking Changes +## Backward-incompatible changes Below is a listing of the breaking change for this release, per subject or integration. Click on one of those to read more about the breaking change @@ -823,7 +823,7 @@ homeassistant: legacy_templates: false ``` -**This feature will be opt-in for this release, the breaking changes below +**This feature will be opt-in for this release, the backward-incompatible changes below only apply if you explicitly enable this new feature.** A template would always result in a string (text). This made it hard diff --git a/source/_posts/2020-11-06-android-300-release.markdown b/source/_posts/2020-11-06-android-300-release.markdown index 009eba74352..ef34635734f 100644 --- a/source/_posts/2020-11-06-android-300-release.markdown +++ b/source/_posts/2020-11-06-android-300-release.markdown @@ -13,9 +13,9 @@ Hey everyone it's been a little while since we last spoke. We have a brand new H Before we get into the release details I'd like to mention that this month marks the [1 year anniversary](https://youtu.be/tc17q1Zn0Xs?t=3487) of the Home Assistant Companion app being offered in the Google Play Store! Just to think how far along the entire app has come from its initial alpha state to what is currently being offered in today's release. Can you believe it's already been a year? -It has been pretty busy over on the Android side of things during Hacktoberfest! We have seen a total of 84 pull requests from a wide range of contributors that we are thankful for, so thank you for all of your efforts! In case you missed it we actually had a release shortly after version 2.4.0 but as we did not have an accompanying blog post, we'll cover whats new since we last spoke in this post. All of the features listed below are already documented on the [Companion](https://companion.home-assistant.io/) site, please be sure to check in there for greater details. Before we continue with what's new lets go over the breaking changes for this release. +It has been pretty busy over on the Android side of things during Hacktoberfest! We have seen a total of 84 pull requests from a wide range of contributors that we are thankful for, so thank you for all of your efforts! In case you missed it we actually had a release shortly after version 2.4.0 but as we did not have an accompanying blog post, we'll cover whats new since we last spoke in this post. All of the features listed below are already documented on the [Companion](https://companion.home-assistant.io/) site, please be sure to check in there for greater details. Before we continue with what's new lets go over the backward-incompatible changes for this release. -## Breaking Changes +## Backward-incompatible changes In our [last blog post](https://www.home-assistant.io/blog/2020/09/12/android-240-release/) we mentioned that we were going to be breaking up some sensors and their attributes. As of 3.0.0 we have completed this task and no longer have non-static attributes as part of any sensor. If you are missing any data please check the Manage Sensors screen under App Configuration and enable the sensor you were previously using as an attribute. @@ -107,7 +107,7 @@ Screenshot of settings. - App language can now be overridden to match a user's profile, this will impact the name of entities that get added as well as the App Configuration appearance. By default your device will use your phones language however, we noticed some users actually prefer Home Assistant to always be in a different language on their device. With this feature you can now set the language to be one of any that are supported by the app. You can also help us translate the app on [Lokalise](https://lokalise.com/public/145814835dd655bc5ab0d0.36753359/). - History of recently received notifications, along with all data that was sent - Notification rate limit information to help you understand if you are about to go over the daily limit. -- Editable widgets, with the ability to delete missing widgets as mentioned in the [breaking changes](#breaking-changes). This is really helpful if you ever created a widget and realized you needed to make one more adjustment. +- Editable widgets, with the ability to delete missing widgets as mentioned in the [backward-incompatible changes](#backward-incompatible-changes). This is really helpful if you ever created a widget and realized you needed to make one more adjustment. - Widgets now update when the screen turns on to provide faster updates - A new widget to control any [media player](https://companion.home-assistant.io/docs/integrations/android-widgets#media-player) diff --git a/source/_posts/2020-11-18-release-118.markdown b/source/_posts/2020-11-18-release-118.markdown index 6cb80b39a50..94015a22f03 100644 --- a/source/_posts/2020-11-18-release-118.markdown +++ b/source/_posts/2020-11-18-release-118.markdown @@ -54,7 +54,7 @@ All in all, a fine release, with an exciting one ahead of us. - [Release 0.118.4 - November 26](#release-01184---november-26) - [Release 0.118.5 - December 5](#release-01185---december-5) - [If you need help...](#if-you-need-help) -- [Breaking Changes](#breaking-changes) +- [Backward-incompatible changes](#backward-incompatible-changes) - [Farewell to the following](#farewell-to-the-following) - [All changes](#all-changes) @@ -170,7 +170,7 @@ more advanced future additions and can significantly reduce the complexity of existing templates in your set up. It should be mostly compatible with your existing templates; However, be sure -to check the breaking changes section for known possible breaking scenarios. +to check the backward-incompatible changes section for known possible breaking scenarios. ## Logbook Card @@ -398,7 +398,7 @@ Experiencing issues introduced by this release? Please report them in our [issue -## Breaking Changes +## Backward-incompatible changes Below is a listing of the breaking change for this release, per subject or integration. Click on one of those to read more about the breaking change diff --git a/source/_posts/2020-12-13-release-202012.markdown b/source/_posts/2020-12-13-release-202012.markdown index 3b90e473eb0..84d50e5ab04 100644 --- a/source/_posts/2020-12-13-release-202012.markdown +++ b/source/_posts/2020-12-13-release-202012.markdown @@ -52,7 +52,7 @@ Happy holidays, stay safe and for the last time this year: Enjoy the release! - [Release 2020.12.1 - December 16](#release-2020121---december-16) - [Release 2020.12.2 - December 30](#release-2020122---december-30) - [If you need help...](#if-you-need-help) -- [Breaking Changes](#breaking-changes) +- [Backward-incompatible changes](#backward-incompatible-changes) - [Farewell to the following](#farewell-to-the-following) - [All changes](#all-changes) @@ -373,7 +373,7 @@ Experiencing issues introduced by this release? Please report them in our [issue -## Breaking Changes +## Backward-incompatible changes Below is a listing of the breaking change for this release, per subject or integration. Click on one of those to read more about the breaking change diff --git a/source/_posts/2021-01-06-release-20211.markdown b/source/_posts/2021-01-06-release-20211.markdown index 273b73b19dd..8805d284eb9 100644 --- a/source/_posts/2021-01-06-release-20211.markdown +++ b/source/_posts/2021-01-06-release-20211.markdown @@ -54,7 +54,7 @@ Enjoy the release! - [Release 2021.1.4 - January 16](#release-202114---january-16) - [Release 2021.1.5 - January 23](#release-202115---january-23) - [If you need help...](#if-you-need-help) -- [Breaking Changes](#breaking-changes) +- [Backward-incompatible changes](#backward-incompatible-changes) - [Farewell to the following](#farewell-to-the-following) - [All changes](#all-changes) @@ -267,7 +267,7 @@ Experiencing issues introduced by this release? Please report them in our [issue -## Breaking Changes +## Backward-incompatible changes Below is a listing of the breaking change for this release, per subject or integration. Click on one of those to read more about the breaking change @@ -494,7 +494,7 @@ Avri has changed their API and it seems not possible to use the new one. - Revert "Change http to auto for cast media image url" ([@emontnemery] - [#44327]) ([cast docs]) - Refactor Airly config flow ([@bieniu] - [#44330]) ([airly docs]) - Update ReCollect docs to use proper name ([@bachya] - [#44291]) ([recollect_waste docs]) -- Upgrade Telegram lib, refactor component for breaking changes ([@ofalvai] - [#44147]) ([telegram_bot docs]) +- Upgrade Telegram lib, refactor component for backward-incompatible changes ([@ofalvai] - [#44147]) ([telegram_bot docs]) - Add new sensors to meteo_france ([@mbo18] - [#44150]) ([meteo_france docs]) - Convert filter tests to use pytest style ([@chrisgramberg678] - [#41743]) ([filter docs]) - Alphabetize hyperion const.py ([@dermotduffy] - [#44343]) ([hyperion docs]) diff --git a/source/_posts/2021-02-03-release-20212.markdown b/source/_posts/2021-02-03-release-20212.markdown index 744cad17bec..55ac3a10b1c 100644 --- a/source/_posts/2021-02-03-release-20212.markdown +++ b/source/_posts/2021-02-03-release-20212.markdown @@ -55,7 +55,7 @@ Enjoy the release! - [Release 2021.2.2 - February 9](#release-202122---february-9) - [Release 2021.2.3 - February 11](#release-202123---february-11) - [If you need help...](#if-you-need-help) -- [Breaking Changes](#breaking-changes) +- [Backward-incompatible changes](#backward-incompatible-changes) - [Farewell to the following](#farewell-to-the-following) - [All changes](#all-changes) @@ -505,7 +505,7 @@ Experiencing issues introduced by this release? Please report them in our [issue -## Breaking Changes +## Backward-incompatible changes Below is a listing of the breaking change for this release, per subject or integration. Click on one of those to read more about the breaking change diff --git a/source/_posts/2021-03-03-release-20213.markdown b/source/_posts/2021-03-03-release-20213.markdown index 0a0de4f0841..f29da97cde8 100644 --- a/source/_posts/2021-03-03-release-20213.markdown +++ b/source/_posts/2021-03-03-release-20213.markdown @@ -45,7 +45,7 @@ My oh my, enjoy this release! - [Release 2021.3.3 - March 8](#release-202133---march-8) - [Release 2021.3.4 - March 12](#release-202134---march-12) - [If you need help...](#if-you-need-help) -- [Breaking Changes](#breaking-changes) +- [Backward-incompatible changes](#backward-incompatible-changes) - [Farewell to the following](#farewell-to-the-following) - [All changes](#all-changes) @@ -522,7 +522,7 @@ Experiencing issues introduced by this release? Please report them in our [issue -## Breaking Changes +## Backward-incompatible changes Below is a listing of the breaking change for this release, per subject or integration. Click on one of those to read more about the breaking change diff --git a/source/_posts/2021-04-07-release-20214.markdown b/source/_posts/2021-04-07-release-20214.markdown index 9c65e839a4d..a741ec825fc 100644 --- a/source/_posts/2021-04-07-release-20214.markdown +++ b/source/_posts/2021-04-07-release-20214.markdown @@ -50,7 +50,7 @@ Enjoy the release! - [Release 2021.4.5 - April 16](#release-202145---april-16) - [Release 2021.4.6 - April 19](#release-202146---april-19) - [If you need help...](#if-you-need-help) -- [Breaking Changes](#breaking-changes) +- [Backward-incompatible changes](#backward-incompatible-changes) - [Farewell to the following](#farewell-to-the-following) - [All changes](#all-changes) @@ -218,7 +218,7 @@ filter the automation list with just the ones that touch your thermostat. So before we talk about The nice new things in Z-Wave JS, there are breaking changes in this release for the Z-Wave JS integration that could affect your -existing automations. Be sure to read the [breaking changes](#breaking-changes) +existing automations. Be sure to read the [backward-incompatible changes](#backward-incompatible-changes) section for more info. Alright, now the fun stuff! You can now configure each Z-Wave device straight @@ -619,7 +619,7 @@ Experiencing issues introduced by this release? Please report them in our [issue -## Breaking Changes +## Backward-incompatible changes Below is a listing of the breaking change for this release, per subject or integration. Click on one of those to read more about the breaking change diff --git a/source/_posts/2021-05-05-release-20215.markdown b/source/_posts/2021-05-05-release-20215.markdown index bda25e8d924..b56b61a740e 100644 --- a/source/_posts/2021-05-05-release-20215.markdown +++ b/source/_posts/2021-05-05-release-20215.markdown @@ -24,7 +24,7 @@ release (which was epic, in my opinion!). But it is not a bad thing! Some really good stability improvements have been introduced this release! Not the hot new items you want to explore immediately, but these fundamental things will really help our systems now and in the future. Making this release an -upgrade that would be a smooth sail for most of us (check the breaking changes). +upgrade that would be a smooth sail for most of us (check the backward-incompatible changes). The most visual part changed this release can be found in the facelift that the integrations dashboard got. Oh, and the new color modes for lights is an amazing @@ -59,7 +59,7 @@ want to tell me who it is...) - [Release 2021.5.4 - May 14](#release-202154---may-14) - [Release 2021.5.5 - May 19](#release-202155---may-19) - [If you need help...](#if-you-need-help) -- [Breaking Changes](#breaking-changes) +- [Backward-incompatible changes](#backward-incompatible-changes) - [Farewell to the following](#farewell-to-the-following) - [All changes](#all-changes) @@ -543,7 +543,7 @@ Experiencing issues introduced by this release? Please report them in our [issue -## Breaking Changes +## Backward-incompatible changes Below is a listing of the breaking change for this release, per subject or integration. Click on one of those to read more about the breaking change diff --git a/source/_posts/2021-06-02-release-20216.markdown b/source/_posts/2021-06-02-release-20216.markdown index 243946f16dd..3a8acdbd75b 100644 --- a/source/_posts/2021-06-02-release-20216.markdown +++ b/source/_posts/2021-06-02-release-20216.markdown @@ -44,10 +44,10 @@ worth scanning the all changes section for your favorite integrations. - [Release 2021.6.5 - June 15](#release-202165---june-15) - [Release 2021.6.6 - June 20](#release-202166---june-20) - [If you need help...](#if-you-need-help) -- [Breaking Changes](#breaking-changes) +- [Backward-incompatible changes](#backward-incompatible-changes) - [Integrations that removed deprecated YAML import](#integrations-that-removed-deprecated-yaml-import) - [Integrations that deprecated YAML import](#integrations-that-deprecated-yaml-import) - - [Other breaking changes](#other-breaking-changes) + - [Other backward-incompatible changes](#other-breaking-changes) - [Farewell to the following](#farewell-to-the-following) - [All changes](#all-changes) @@ -471,9 +471,9 @@ Experiencing issues introduced by this release? Please report them in our [issue -## Breaking Changes +## Backward-incompatible changes -This release has an unusual amount of breaking changes to report. Don't worry, +This release has an unusual amount of backward-incompatible changes to report. Don't worry, most won't have a noticeable impact and are part of a cleanup effort. However, we do want to report them all, just to be complete and transparent. @@ -535,7 +535,7 @@ deprecation period. - [Transmission][transmission docs] - [VeSync][vesync docs] -### Other breaking changes +### Other backward-incompatible changes Below is a listing of the other breaking change for this release, per subject or integration. Click on one of those to read more about the breaking change diff --git a/source/_posts/2021-07-07-release-20217.markdown b/source/_posts/2021-07-07-release-20217.markdown index 275d5449836..b10ca2ec7ce 100644 --- a/source/_posts/2021-07-07-release-20217.markdown +++ b/source/_posts/2021-07-07-release-20217.markdown @@ -54,7 +54,7 @@ Alright, that's it! Enjoy the release! - [Release 2021.7.3 - July 16](#release-202173---july-16) - [Release 2021.7.4 - July 21](#release-202174---july-21) - [If you need help...](#if-you-need-help) -- [Breaking Changes](#breaking-changes) +- [Backward-incompatible changes](#backward-incompatible-changes) - [All changes](#all-changes) ## New entity: Select @@ -580,7 +580,7 @@ Experiencing issues introduced by this release? Please report them in our [issue -## Breaking Changes +## Backward-incompatible changes Below is a listing of the breaking change for this release, per subject or integration. Click on one of those to read more about the breaking change @@ -690,7 +690,7 @@ In this release, the content of this table is reset. This does not impact any state history and this data isn't used by Home Assistant as of yet. If you have no idea what this message is about, you can safely ignore it. -We have merely listed this to be complete in our breaking changes report. +We have merely listed this to be complete in our backward-incompatible changes report. ([@emontnemery] - [#52331]) ([history docs]) diff --git a/source/_posts/2021-08-04-release-20218.markdown b/source/_posts/2021-08-04-release-20218.markdown index e7dfcb3cdc7..03cb2a00cc5 100644 --- a/source/_posts/2021-08-04-release-20218.markdown +++ b/source/_posts/2021-08-04-release-20218.markdown @@ -68,7 +68,7 @@ later today (9:00 PM CET). - [Release 2021.8.7 - August 15](#release-202187---august-15) - [Release 2021.8.8 - August 18](#release-202188---august-18) - [If you need help...](#if-you-need-help) -- [Breaking Changes](#breaking-changes) +- [Backward-incompatible changes](#backward-incompatible-changes) - [Farewell to the following](#farewell-to-the-following) - [All changes](#all-changes) @@ -650,7 +650,7 @@ Experiencing issues introduced by this release? Please report them in our [issue -## Breaking Changes +## Backward-incompatible changes Below is a listing of the breaking change for this release, per subject or integration. Click on one of those to read more about the breaking change diff --git a/source/_posts/2021-09-01-release-20219.markdown b/source/_posts/2021-09-01-release-20219.markdown index 0cdd2496ff3..74be0966289 100644 --- a/source/_posts/2021-09-01-release-20219.markdown +++ b/source/_posts/2021-09-01-release-20219.markdown @@ -43,7 +43,7 @@ Enjoy another great release! Be sure to tune into [the 2021.9 Release Party on Y - [Release 2021.9.6 - September 11](#release-202196---september-11) - [Release 2021.9.7 - September 18](#release-202197---september-18) - [If you need help...](#if-you-need-help) -- [Breaking Changes](#breaking-changes) +- [Backward-incompatible changes](#backward-incompatible-changes) - [All changes](#all-changes) ## Home Energy Management updates @@ -629,7 +629,7 @@ Experiencing issues introduced by this release? Please report them in our [issue -## Breaking Changes +## Backward-incompatible changes Below is a listing of the breaking change for this release, per subject or integration. Click on one of those to read more about the breaking change @@ -1440,7 +1440,7 @@ developer blog about it: - Add Gas device class to DSMR Reader ([@frenck] - [#54748]) ([dsmr_reader docs]) - Tibber data coordinator ([@Danielhiversen] - [#53619]) ([tibber docs]) - Add select platform for Xiaomi Miio fans ([@bieniu] - [#54702]) ([xiaomi_miio docs]) (breaking-change) -- Bump async-upnp-client to 0.20.0, adapt to breaking changes ([@bdraco] - [#54782]) ([upnp docs]) ([dlna_dmr docs]) ([ssdp docs]) +- Bump async-upnp-client to 0.20.0, adapt to backward-incompatible changes ([@bdraco] - [#54782]) ([upnp docs]) ([dlna_dmr docs]) ([ssdp docs]) - Remove unused last_reset from Toon ([@emontnemery] - [#54798]) ([toon docs]) - Remove last_reset and update state class for Atome energy ([@emontnemery] - [#54801]) ([atome docs]) - Remove distro from updater requirements ([@ludeeus] - [#54804]) ([updater docs]) diff --git a/source/_posts/2021-10-06-release-202110.markdown b/source/_posts/2021-10-06-release-202110.markdown index 9c8603aedbf..8bf7d130004 100644 --- a/source/_posts/2021-10-06-release-202110.markdown +++ b/source/_posts/2021-10-06-release-202110.markdown @@ -65,7 +65,7 @@ Enjoy the release! - [Release 2021.10.6 - October 18](#release-2021106---october-18) - [Release 2021.10.7 - November 1](#release-2021107---november-1) - [If you need help...](#if-you-need-help) -- [Breaking Changes](#breaking-changes) +- [Backward-incompatible changes](#backward-incompatible-changes) - [Farewell to the following](#farewell-to-the-following) - [All changes](#all-changes) @@ -160,7 +160,7 @@ Some really useful new MDI icons have been added in this release! Several icons have been removed or renamed in v6, but we have ensured they will keep working for the upcoming two releases. Home Assistant will write warnings in the logs in case you are using one of the affected icons. -The breaking changes section has more information about this. +The backward-incompatible changes section has more information about this. [mdi]: https://pictogrammers.com/library/mdi/ @@ -527,7 +527,7 @@ Experiencing issues introduced by this release? Please report them in our [issue -## Breaking Changes +## Backward-incompatible changes Below is a listing of the breaking change for this release, per subject or integration. Click on one of those to read more about the breaking change diff --git a/source/_posts/2021-11-03-release-202111.markdown b/source/_posts/2021-11-03-release-202111.markdown index 4ceb2d3322f..3282d9e360a 100644 --- a/source/_posts/2021-11-03-release-202111.markdown +++ b/source/_posts/2021-11-03-release-202111.markdown @@ -67,7 +67,7 @@ Enjoy the release! - [Release 2021.11.4 - November 15](#release-2021114---november-15) - [Release 2021.11.5 - November 19](#release-2021115---november-19) - [If you need help...](#if-you-need-help) -- [Breaking Changes](#breaking-changes) +- [Backward-incompatible changes](#backward-incompatible-changes) - [Farewell to the following](#farewell-to-the-following) - [All changes](#all-changes) @@ -167,8 +167,8 @@ diagnostic entities), we now do the following: or area the device is in. They are only called if explicitly called by their entity ID. -Please note, the above-listed points are breaking changes, also listed in -the breaking changes section of these release notes. +Please note, the above-listed points are backward-incompatible changes, also listed in +the backward-incompatible changes section of these release notes. Like the previous visit device or service feature, this new organization capability has been adopted by many of our maintainers: 60+ integrations! @@ -613,7 +613,7 @@ Experiencing issues introduced by this release? Please report them in our [issue -## Breaking Changes +## Backward-incompatible changes Below is a listing of the breaking change for this release, per subject or integration. Click on one of those to read more about the breaking change diff --git a/source/_posts/2021-12-11-release-202112.markdown b/source/_posts/2021-12-11-release-202112.markdown index c83da3a4ecf..950bf9282a6 100644 --- a/source/_posts/2021-12-11-release-202112.markdown +++ b/source/_posts/2021-12-11-release-202112.markdown @@ -61,7 +61,7 @@ holidays. So, the first release in 2022, will be Wednesday, 2 February 2022._ - [Release 2021.12.9 - January 10](#release-2021129---january-10) - [Release 2021.12.10 - January 17](#release-20211210---january-17) - [If you need help...](#if-you-need-help) -- [Breaking Changes](#breaking-changes) +- [Backward-incompatible changes](#backward-incompatible-changes) - [Updates for custom integration developers](#updates-for-custom-integration-developers) - [Farewell to the following](#farewell-to-the-following) - [All changes](#all-changes) @@ -1059,7 +1059,7 @@ Experiencing issues introduced by this release? Please report them in our [issue -## Breaking Changes +## Backward-incompatible changes Below is a listing of the breaking change for this release, per subject or integration. Click on one of those to read more about the breaking change diff --git a/source/_posts/2022-02-02-release-20222.markdown b/source/_posts/2022-02-02-release-20222.markdown index 9a0cb6c6f67..661c59ad4fc 100644 --- a/source/_posts/2022-02-02-release-20222.markdown +++ b/source/_posts/2022-02-02-release-20222.markdown @@ -25,7 +25,7 @@ Over 2,500 contributions make this release the largest one we have ever shipped! Including 15 brand-new integrations and 13 existing integrations, which are now available to set up via the user interface. -Now don't be scared when you look at the breaking changes section. It is a lot, +Now don't be scared when you look at the backward-incompatible changes section. It is a lot, however, most of those are cleanup of old deprecations, or caused by things moving to the UI. No better way to start a fresh year, than by cleaning up 🧹 @@ -65,7 +65,7 @@ Enjoy the release! - [Release 2022.2.8 - February 16](#release-202228---february-16) - [Release 2022.2.9 - February 18](#release-202229---february-18) - [If you need help...](#if-you-need-help) -- [Breaking Changes](#breaking-changes) +- [Backward-incompatible changes](#backward-incompatible-changes) - [Farewell to the following](#farewell-to-the-following) - [All changes](#all-changes) @@ -1021,7 +1021,7 @@ Experiencing issues introduced by this release? Please report them in our [issue -## Breaking Changes +## Backward-incompatible changes Below is a listing of the breaking change for this release, per subject or integration. Click on one of those to read more about the breaking change diff --git a/source/_posts/2022-02-08-android-february.markdown b/source/_posts/2022-02-08-android-february.markdown index 66f9644eef2..b685bf0956c 100644 --- a/source/_posts/2022-02-08-android-february.markdown +++ b/source/_posts/2022-02-08-android-february.markdown @@ -14,7 +14,7 @@ og_image: /images/blog/2022-02-android/Companion.png Hey Everyone! It's time for the next Android release and we are really excited to get this one out. Lots of changes for all versions of the app, including Wear OS and Quest devices. -## Breaking Changes +## Backward-incompatible changes We have a pretty big release this month with a lot of changes going on. Some of these changes are noticeable as soon as you update the app, so let's cover those first. @@ -42,7 +42,7 @@ A big thank you to [JBassett] for kicking off this feature and working hard to s ### Sensor Changes -The remaining breaking changes in this release are related to 2 sensors offered by all versions of the app. +The remaining backward-incompatible changes in this release are related to 2 sensors offered by all versions of the app. - [Do Not Disturb Sensor] - No longer available on devices running Android 5 or lower. This sensor, which was previously offered to all supported Android versions, has been updated to use the official Android API instead of the undocumented one. The Android API is only available on devices running Android 6+. Older devices will no longer see this sensor in the Manage Sensors screen. - [Last Used App Sensor] - This sensor previously reported its state as the application label. We realized that this is not always unique, multiple apps can have the exact same name. The state has changed to report the package id which is guaranteed to be unique. The application name is now available as an attribute. @@ -53,7 +53,7 @@ This next feature of the release is also going to be immediately noticeable upon  -The changelog prompt will be maintained by contributors of the app as we do not think it will be user friendly to show GitHub commit messages. This allows us to highlight the above breaking changes to all users so they no longer have surprises going forward. Thank you to [dshokouhi] for adding this feature. +The changelog prompt will be maintained by contributors of the app as we do not think it will be user friendly to show GitHub commit messages. This allows us to highlight the above backward-incompatible changes to all users so they no longer have surprises going forward. Thank you to [dshokouhi] for adding this feature. ## Wear OS Updates diff --git a/source/_posts/2022-03-02-release-20223.markdown b/source/_posts/2022-03-02-release-20223.markdown index c22892dd417..ae8e1f551ca 100644 --- a/source/_posts/2022-03-02-release-20223.markdown +++ b/source/_posts/2022-03-02-release-20223.markdown @@ -59,7 +59,7 @@ Enjoy the release! - [Release 2022.3.7 - March 23](#release-202237---march-23) - [Release 2022.3.8 - March 29](#release-202238---march-29) - [Need help? Join the community!](#need-help-join-the-community) -- [Breaking Changes](#breaking-changes) +- [Backward-incompatible changes](#backward-incompatible-changes) - [Updates for custom integration developers](#updates-for-custom-integration-developers) - [Farewell to the following](#farewell-to-the-following) - [All changes](#all-changes) @@ -692,7 +692,7 @@ into your inbox. -## Breaking Changes +## Backward-incompatible changes Below is a listing of the breaking change for this release, per subject or integration. Click on one of those to read more about the breaking change @@ -1277,7 +1277,7 @@ You can find more information on the new dependency resolver in Python pip here: {% details "async_timeout()" %} We now use version 3.8+ of `aiohttp`, which requires `async_timeout` 4.0+ -which has multiple breaking changes: +which has multiple backward-incompatible changes: - `async_timeout.timeout` drops the `loop=` keyword arg. - `async_timeout.current_task` has been removed. diff --git a/source/_posts/2022-04-06-release-20224.markdown b/source/_posts/2022-04-06-release-20224.markdown index 7aacb4300e5..c521c2fb998 100644 --- a/source/_posts/2022-04-06-release-20224.markdown +++ b/source/_posts/2022-04-06-release-20224.markdown @@ -65,7 +65,7 @@ Enjoy the release! - [Release 2022.4.6 - April 20](#release-202246---april-20) - [Release 2022.4.7 - April 24](#release-202247---april-24) - [Need help? Join the community!](#need-help-join-the-community) -- [Breaking Changes](#breaking-changes) +- [Backward-incompatible changes](#backward-incompatible-changes) - [Farewell to the following](#farewell-to-the-following) - [All changes](#all-changes) @@ -1052,7 +1052,7 @@ other news about the Open Home; straight into your inbox. -## Breaking Changes +## Backward-incompatible changes Below is a listing of the breaking change for this release, per subject or integration. Click on one of those to read more about the breaking change diff --git a/source/_posts/2022-05-04-release-20225.markdown b/source/_posts/2022-05-04-release-20225.markdown index ec992e35922..c0f20cd1bc2 100644 --- a/source/_posts/2022-05-04-release-20225.markdown +++ b/source/_posts/2022-05-04-release-20225.markdown @@ -67,7 +67,7 @@ Enjoy the release! - [Release 2022.5.4 - May 12](#release-202254---may-12) - [Release 2022.5.5 - May 18](#release-202255---may-18) - [Need help? Join the community!](#need-help-join-the-community) -- [Breaking Changes](#breaking-changes) +- [Backward-incompatible changes](#backward-incompatible-changes) - [Farewell to the following](#farewell-to-the-following) - [All changes](#all-changes) @@ -99,7 +99,7 @@ logical place for YAML configuration checks and reloading. You might notice some of the new menu items are fairly empty. For those menus, like "Storage" and "Hardware", we have more content planned soon! -Just to be sure, we have added a list of changes to the breaking changes section; +Just to be sure, we have added a list of changes to the backward-incompatible changes section; please check those out in case you are missing something. ## Find entities even quicker than before @@ -956,7 +956,7 @@ Are you more into email? [Sign-up for our Building the Open Home Newsletter](/ne to get the latest news about features, things happening in our community and other news about building an Open Home; straight into your inbox. -## Breaking Changes +## Backward-incompatible changes Below is a listing of the breaking change for this release, per subject or integration. Click on one of those to read more about the breaking change diff --git a/source/_posts/2022-06-01-release-20226.markdown b/source/_posts/2022-06-01-release-20226.markdown index 78f589c1019..dab203dcdce 100644 --- a/source/_posts/2022-06-01-release-20226.markdown +++ b/source/_posts/2022-06-01-release-20226.markdown @@ -67,7 +67,7 @@ Enjoy the release (and upcoming events)! - [Release 2022.6.6 - June 14](#release-202266---june-14) - [Release 2022.6.7 - June 22](#release-202267---june-22) - [Need help? Join the community!](#need-help-join-the-community) -- [Breaking Changes](#breaking-changes) +- [Backward-incompatible changes](#backward-incompatible-changes) - [Farewell to the following](#farewell-to-the-following) - [All changes](#all-changes) @@ -727,9 +727,9 @@ Are you more into email? [Sign-up for our Building the Open Home Newsletter](/ne to get the latest news about features, things happening in our community and other news about building an Open Home; straight into your inbox. -## Breaking Changes +## Backward-incompatible changes -Below is a listing of the breaking changes for this release, per subject or +Below is a listing of the backward-incompatible changes for this release, per subject or integration. Click on one of those to read more about the breaking change for that specific item. diff --git a/source/_posts/2022-07-06-release-20227.markdown b/source/_posts/2022-07-06-release-20227.markdown index d36947aca16..2a8b436c1ef 100644 --- a/source/_posts/2022-07-06-release-20227.markdown +++ b/source/_posts/2022-07-06-release-20227.markdown @@ -59,7 +59,7 @@ like. So without further due: Enjoy the release! - [Release 2022.7.6 - July 20](#release-202276---july-20) - [Release 2022.7.7 - July 26](#release-202277---july-26) - [Need help? Join the community!](#need-help-join-the-community) -- [Breaking Changes](#breaking-changes) +- [Backward-incompatible changes](#backward-incompatible-changes) - [Farewell to the following](#farewell-to-the-following) - [All changes](#all-changes) @@ -767,7 +767,7 @@ Are you more into email? [Sign-up for our Building the Open Home Newsletter](/ne to get the latest news about features, things happening in our community and [](https://github.com/home-assistant/core/pull/58768)other news about building an Open Home; straight into your inbox. -## Breaking Changes +## Backward-incompatible changes Below is a listing of the breaking change for this release, per subject or integration. Click on one of those to read more about the breaking change diff --git a/source/_posts/2022-08-03-release-20228.markdown b/source/_posts/2022-08-03-release-20228.markdown index 07c2f87b754..9142c524102 100644 --- a/source/_posts/2022-08-03-release-20228.markdown +++ b/source/_posts/2022-08-03-release-20228.markdown @@ -51,7 +51,7 @@ Enjoy the release! - [Release 2022.8.6 - August 17](#release-202286---august-17) - [Release 2022.8.7 - August 25](#release-202287---august-25) - [Need help? Join the community!](#need-help-join-the-community) -- [Breaking Changes](#breaking-changes) +- [Backward-incompatible changes](#backward-incompatible-changes) - [Farewell to the following](#farewell-to-the-following) - [All changes](#all-changes) @@ -673,7 +673,7 @@ Are you more into email? [Sign-up for our Building the Open Home Newsletter](/ne to get the latest news about features, things happening in our community and other news about building an Open Home; straight into your inbox. -## Breaking Changes +## Backward-incompatible changes Below is a listing of the breaking change for this release, per subject or integration. Click on one of those to read more about the breaking change diff --git a/source/_posts/2022-09-07-release-20229.markdown b/source/_posts/2022-09-07-release-20229.markdown index 29acdc552e9..0a82f25b608 100644 --- a/source/_posts/2022-09-07-release-20229.markdown +++ b/source/_posts/2022-09-07-release-20229.markdown @@ -45,7 +45,7 @@ Now I know that everyone usually expects [@frenck] to be writing these release n - [Release 2022.9.6 - September 22](#release-202296---september-22) - [Release 2022.9.7 - September 26](#release-202297---september-26) - [Need help? Join the community](#need-help-join-the-community) -- [Breaking Changes](#breaking-changes) +- [Backward-incompatible changes](#backward-incompatible-changes) - [All changes](#all-changes) Don't forget to [join our release party live stream on YouTube](https://www.youtube.com/watch?v=UTltO1-d56s) today at 12:00 PDT / 21:00 CET! @@ -764,7 +764,7 @@ Are you more into email? [Sign-up for our Building the Open Home Newsletter](/ne to get the latest news about features, things happening in our community and other news about building an Open Home; straight into your inbox. -## Breaking Changes +## Backward-incompatible changes Below is a listing of the breaking change for this release, per subject or integration. Click on one of those to read more about the breaking change diff --git a/source/_posts/2022-10-05-release-202210.markdown b/source/_posts/2022-10-05-release-202210.markdown index 046618d70d4..d515087c53e 100644 --- a/source/_posts/2022-10-05-release-202210.markdown +++ b/source/_posts/2022-10-05-release-202210.markdown @@ -57,7 +57,7 @@ PS: I noticed the [Home Assistant SkyConnect is now available for pre-order](/sk - [Release 2022.10.4 - October 14](#release-2022104---october-14) - [Release 2022.10.5 - October 20](#release-2022105---october-20) - [Need help? Join the community!](#need-help-join-the-community) -- [Breaking Changes](#breaking-changes) +- [Backward-incompatible changes](#backward-incompatible-changes) - [Farewell to the following](#farewell-to-the-following) - [All changes](#all-changes) @@ -672,7 +672,7 @@ Are you more into email? [Sign-up for our Building the Open Home Newsletter](/ne to get the latest news about features, things happening in our community and other news about building an Open Home; straight into your inbox. -## Breaking Changes +## Backward-incompatible changes Below is a listing of the breaking change for this release, per subject or integration. Click on one of those to read more about the breaking change @@ -821,7 +821,7 @@ the state no longer reports as "ok" but instead reports as "on". {% details "Radarr" %} -Some breaking changes have been made in disabling the Movies count sensor out +Some backward-incompatible changes have been made in disabling the Movies count sensor out of caution. This sensor can cause problems with massive databases. If you still wish to use it, you may do so. diff --git a/source/_posts/2022-11-02-release-202211.markdown b/source/_posts/2022-11-02-release-202211.markdown index f79b263eb05..4d7f1bd320a 100644 --- a/source/_posts/2022-11-02-release-202211.markdown +++ b/source/_posts/2022-11-02-release-202211.markdown @@ -58,7 +58,7 @@ Sunday, November 13, 2022 (11:00 AM PST / 20:00 CET). - [Release 2022.11.4 - November 20](#release-2022114---november-20) - [Release 2022.11.5 - November 30](#release-2022115---november-30) - [Need help? Join the community!](#need-help-join-the-community) -- [Breaking Changes](#breaking-changes) +- [Backward-incompatible changes](#backward-incompatible-changes) - [All changes](#all-changes) ## Tile card @@ -794,7 +794,7 @@ Are you more into email? [Sign-up for our Building the Open Home Newsletter](/ne to get the latest news about features, things happening in our community and other news about building an Open Home; straight into your inbox. -## Breaking Changes +## Backward-incompatible changes Below is a listing of the breaking change for this release, per subject or integration. Click on one of those to read more about the breaking change diff --git a/source/_posts/2022-12-07-release-202212.markdown b/source/_posts/2022-12-07-release-202212.markdown index e0811c200ff..e71242d0a74 100644 --- a/source/_posts/2022-12-07-release-202212.markdown +++ b/source/_posts/2022-12-07-release-202212.markdown @@ -70,7 +70,7 @@ Happy holidays and for the last time in 2022: Enjoy the release! - [Release 2022.12.8 - December 21](#release-2022128---december-21) - [Release 2022.12.9 - January, 2](#release-2022129---january-2) - [Need help? Join the community!](#need-help-join-the-community) -- [Breaking Changes](#breaking-changes) +- [Backward-incompatible changes](#backward-incompatible-changes) - [Farewell to the following](#farewell-to-the-following) - [All changes](#all-changes) @@ -708,7 +708,7 @@ Are you more into email? [Sign-up for our Building the Open Home Newsletter](/ne to get the latest news about features, things happening in our community and other news about building an Open Home; straight into your inbox. -## Breaking Changes +## Backward-incompatible changes {% details "Cloudflare" %} @@ -1096,7 +1096,7 @@ each PoE-capable port without mapping it to a client. {% enddetails %} If you are a custom integration or theme developer and want to learn about -breaking changes and new features available for your integration: Be sure to +backward-incompatible changes and new features available for your integration: Be sure to follow our [developer blog][devblog]. The following are the most notable for this release: diff --git a/source/_posts/2023-01-04-release-20231.markdown b/source/_posts/2023-01-04-release-20231.markdown index 2fdf83ebd1c..b0626a93511 100644 --- a/source/_posts/2023-01-04-release-20231.markdown +++ b/source/_posts/2023-01-04-release-20231.markdown @@ -56,7 +56,7 @@ PS: Did you know [Home Assistant is now on Mastodon](https://fosstodon.org/@home - [Release 2023.1.6 - January 19](#release-202316---january-19) - [Release 2023.1.7 - January 22](#release-202317---january-22) - [Need help? Join the community!](#need-help-join-the-community) -- [Breaking Changes](#breaking-changes) +- [Backward-incompatible changes](#backward-incompatible-changes) - [Farewell to the following](#farewell-to-the-following) - [All changes](#all-changes) @@ -637,7 +637,7 @@ Are you more into email? [Sign-up for our Building the Open Home Newsletter](/ne to get the latest news about features, things happening in our community and other news about building an Open Home; straight into your inbox. -## Breaking Changes +## Backward-incompatible changes {% details "Image Upload / Default Config" %} diff --git a/source/_posts/2023-02-01-release-20232.markdown b/source/_posts/2023-02-01-release-20232.markdown index 99ee1998b6e..db5e7606d37 100644 --- a/source/_posts/2023-02-01-release-20232.markdown +++ b/source/_posts/2023-02-01-release-20232.markdown @@ -54,7 +54,7 @@ _PS: Just a reminder that valentine's day is coming up. Be sure to share the lov - [Release 2023.2.4 - February 13](#release-202324---february-13) - [Release 2023.2.5 - February 15](#release-202325---february-15) - [Need help? Join the community!](#need-help-join-the-community) -- [Breaking Changes](#breaking-changes) +- [Backward-incompatible changes](#backward-incompatible-changes) - [Farewell to the following](#farewell-to-the-following) - [All changes](#all-changes) @@ -733,7 +733,7 @@ Are you more into email? [Sign-up for our Building the Open Home Newsletter](/ne to get the latest news about features, things happening in our community and other news about building an Open Home; straight into your inbox. -## Breaking Changes +## Backward-incompatible changes {% details "Python 3.9 support has been removed" %} diff --git a/source/_posts/2023-03-01-release-20233.markdown b/source/_posts/2023-03-01-release-20233.markdown index 33f28c9dada..6a6242eb22c 100644 --- a/source/_posts/2023-03-01-release-20233.markdown +++ b/source/_posts/2023-03-01-release-20233.markdown @@ -55,7 +55,7 @@ Enjoy the release! - [Release 2023.3.5 - March 16](#release-202335---march-16) - [Release 2023.3.6 - March 22](#release-202336---march-22) - [Need help? Join the community!](#need-help-join-the-community) -- [Breaking Changes](#breaking-changes) +- [Backward-incompatible changes](#backward-incompatible-changes) - [All changes](#all-changes) Don't forget to [join our release party live stream on YouTube](https://www.youtube.com/watch?v=3UaLAhG9Brc) 1 March 2023, at 12:00 PST / 21:00 CET! @@ -699,7 +699,7 @@ Are you more into email? [Sign-up for our Building the Open Home Newsletter](/ne to get the latest news about features, things happening in our community and other news about building an Open Home; straight into your inbox. -## Breaking Changes +## Backward-incompatible changes {% details "Assist / Conversation" %} diff --git a/source/_posts/2023-04-05-release-20234.markdown b/source/_posts/2023-04-05-release-20234.markdown index 8aefff9d92e..b58cf74e2a2 100644 --- a/source/_posts/2023-04-05-release-20234.markdown +++ b/source/_posts/2023-04-05-release-20234.markdown @@ -51,7 +51,7 @@ Happy Easter! 🐣 and enjoy the release! - [Release 2023.4.5 - April 17](#release-202345---april-17) - [Release 2023.4.6 - April 21](#release-202346---april-21) - [Need help? Join the community!](#need-help-join-the-community) -- [Breaking Changes](#breaking-changes) +- [Backward-incompatible changes](#backward-incompatible-changes) - [Farewell to the following](#farewell-to-the-following) - [All changes](#all-changes) @@ -950,7 +950,7 @@ Are you more into email? [Sign-up for our Building the Open Home Newsletter](/ne to get the latest news about features, things happening in our community and other news about building an Open Home; straight into your inbox. -## Breaking Changes +## Backward-incompatible changes {% details "Aladdin Connect" %} diff --git a/source/_posts/2023-05-03-release-20235.markdown b/source/_posts/2023-05-03-release-20235.markdown index 33efa5c1459..aeab18b4d8e 100644 --- a/source/_posts/2023-05-03-release-20235.markdown +++ b/source/_posts/2023-05-03-release-20235.markdown @@ -52,7 +52,7 @@ Enjoy the release! - [Release 2023.5.3 - May 14](#release-202353---may-14) - [Release 2023.5.4 - May 23](#release-202354---may-23) - [Need help? Join the community!](#need-help-join-the-community) -- [Breaking Changes](#breaking-changes) +- [Backward-incompatible changes](#backward-incompatible-changes) - [Farewell to the following](#farewell-to-the-following) - [All changes](#all-changes) @@ -657,7 +657,7 @@ Are you more into email? [Sign-up for our Building the Open Home Newsletter](/ne to get the latest news about features, things happening in our community and other news about building an Open Home; straight into your inbox. -## Breaking Changes +## Backward-incompatible changes {% details "Accuweather" %} diff --git a/source/_posts/2023-06-07-release-20236.markdown b/source/_posts/2023-06-07-release-20236.markdown index e29efd98bbb..c46258ed413 100644 --- a/source/_posts/2023-06-07-release-20236.markdown +++ b/source/_posts/2023-06-07-release-20236.markdown @@ -52,7 +52,7 @@ Enjoy the release! - [Release 2023.6.2 - June 14](#release-202362---june-14) - [Release 2023.6.3 - June 23](#release-202363---june-23) - [Need help? Join the community!](#need-help-join-the-community) -- [Breaking Changes](#breaking-changes) +- [Backward-incompatible changes](#backward-incompatible-changes) - [Farewell to the following](#farewell-to-the-following) - [All changes](#all-changes) @@ -725,7 +725,7 @@ Are you more into email? [Sign-up for our Building the Open Home Newsletter](/ne to get the latest news about features, things happening in our community and other news about building an Open Home; straight into your inbox. -## Breaking Changes +## Backward-incompatible changes {% details "Python" %} diff --git a/source/_posts/2023-07-05-release-20237.markdown b/source/_posts/2023-07-05-release-20237.markdown index d9249f8b687..9ec31648cc3 100644 --- a/source/_posts/2023-07-05-release-20237.markdown +++ b/source/_posts/2023-07-05-release-20237.markdown @@ -1,7 +1,7 @@ --- layout: post title: "2023.7: Responding services" -description: "Services can now respond with data, a new dialog for lock, sentence triggers, fewer breaking changes, Bluetooth proxies are now the fastest option, copy 'n paste in dashboards, brand new image entities, a dashboard action to open assist, climate support for Matter, and more!" +description: "Services can now respond with data, a new dialog for lock, sentence triggers, fewer backward-incompatible changes, Bluetooth proxies are now the fastest option, copy 'n paste in dashboards, brand new image entities, a dashboard action to open assist, climate support for Matter, and more!" date: 2023-07-05 00:00:00 date_formatted: "July 5, 2023" author: Franck Nijhof @@ -53,7 +53,7 @@ Enjoy the release! - [New script dialog](#new-script-dialog) - [Lightning fast Bluetooth proxies](#lightning-fast-bluetooth-proxies) - [Matter updates](#matter-updates) -- [Reducing the risk of running into breaking changes](#reducing-the-risk-of-running-into-breaking-changes) +- [Reducing the risk of running into backward-incompatible changes](#reducing-the-risk-of-running-into-breaking-changes) - [Other noteworthy changes](#other-noteworthy-changes) - [New integrations](#new-integrations) - [Release 2023.7.1 - July 6](#release-202371---july-6) @@ -61,7 +61,7 @@ Enjoy the release! - [Release 2023.7.3 - July 21](#release-202373---july-21) - [Integrations now available to set up from the UI](#integrations-now-available-to-set-up-from-the-ui) - [Need help? Join the community!](#need-help-join-the-community) -- [Breaking changes](#breaking-changes) +- [Backward-incompatible changes](#backward-incompatible-changes) - [Farewell to the following](#farewell-to-the-following) - [All changes](#all-changes) @@ -332,9 +332,9 @@ This means if you have a [Nest Thermostat](https://support.google.com/googlenest (not the E or learning ones) with the latest firmware, you can now use it directly with Home Assistant, entirely local without clouds! -## Reducing the risk of running into breaking changes +## Reducing the risk of running into backward-incompatible changes -Breaking changes, nobody loves them, but they are sometimes necessary to move +Backward-incompatible changes, nobody loves them, but they are sometimes necessary to move forward. We try to keep them to an absolute minimum, but sometimes they are inevitable. @@ -795,7 +795,7 @@ Are you more into email? [Sign-up for our Building the Open Home Newsletter](/ne to get the latest news about features, things happening in our community and other news about building an Open Home; straight into your inbox. -## Breaking changes +## Backward-incompatible changes {% details "Home Assistant Container (Docker)" %} diff --git a/source/_posts/2023-08-02-release-20238.markdown b/source/_posts/2023-08-02-release-20238.markdown index 6c17dd73be6..7740bf94110 100644 --- a/source/_posts/2023-08-02-release-20238.markdown +++ b/source/_posts/2023-08-02-release-20238.markdown @@ -57,7 +57,7 @@ Enjoy the release! - [Release 2023.8.3 - August 18](#release-202383---august-18) - [Release 2023.8.4 - August 24](#release-202384---august-24) - [Need help? Join the community!](#need-help-join-the-community) -- [Breaking changes](#breaking-changes) +- [Backward-incompatible changes](#backward-incompatible-changes) - [Farewell to the following](#farewell-to-the-following) - [All changes](#all-changes) @@ -737,7 +737,7 @@ Are you more into email? [Sign-up for our Building the Open Home Newsletter](/ne to get the latest news about features, things happening in our community and other news about building an Open Home; straight into your inbox. -## Breaking changes +## Backward-incompatible changes {% details "Python 3.10 support has been removed" %} @@ -926,7 +926,7 @@ changes and new features available for your integration: Be sure to follow our 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 breaking changes above for more information. + 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. diff --git a/source/_posts/2023-09-06-release-20239.markdown b/source/_posts/2023-09-06-release-20239.markdown index 53834330ba8..d6d4d7e042c 100644 --- a/source/_posts/2023-09-06-release-20239.markdown +++ b/source/_posts/2023-09-06-release-20239.markdown @@ -48,7 +48,7 @@ Bram - [Release 2023.9.2 - September 12](#release-202392---september-12) - [Release 2023.9.3 - September 24](#release-202393---september-24) - [Need help? Join the community!](#need-help-join-the-community) -- [Breaking changes](#breaking-changes) +- [Backward-incompatible changes](#backward-incompatible-changes) - [All changes](#all-changes) Don't forget to [join our release party live stream on YouTube](https://www.youtube.com/watch?v=JSNRrWk9IHs) @@ -644,7 +644,7 @@ Are you more into email? [Sign-up for our Building the Open Home Newsletter](/ne to get the latest news about features, things happening in our community and other news about building an Open Home; straight into your inbox. -## Breaking changes +## Backward-incompatible changes {% details "BMW Connected Drive" %} diff --git a/source/_posts/2023-10-04-release-202310.markdown b/source/_posts/2023-10-04-release-202310.markdown index e59747a8641..b39049ce58e 100644 --- a/source/_posts/2023-10-04-release-202310.markdown +++ b/source/_posts/2023-10-04-release-202310.markdown @@ -45,7 +45,7 @@ Enjoy the release! - [Release 2023.10.4 - October 21](#release-2023104---october-21) - [Release 2023.10.5 - October 22](#release-2023105---october-22) - [Need help? Join the community!](#need-help-join-the-community) -- [Breaking changes](#breaking-changes) +- [Backward-incompatible changes](#backward-incompatible-changes) - [All changes](#all-changes) Don't forget to [join our release party live stream on YouTube](https://www.youtube.com/watch?v=-GDonruFfKc) @@ -588,7 +588,7 @@ Are you more into email? [Sign-up for our Building the Open Home Newsletter](/ne to get the latest news about features, things happening in our community and other news about building an Open Home; straight into your inbox. -## Breaking changes +## Backward-incompatible changes {% details "HomeKit Bridge" %} diff --git a/source/_posts/2023-11-01-release-202311.markdown b/source/_posts/2023-11-01-release-202311.markdown index 5de31ab3323..412dc111551 100644 --- a/source/_posts/2023-11-01-release-202311.markdown +++ b/source/_posts/2023-11-01-release-202311.markdown @@ -60,7 +60,7 @@ Enjoy the release! - [Release 2023.11.1 - November 4](#release-2023111---november-4) - [Release 2023.11.2 - November 10](#release-2023112---november-10) - [Need help? Join the community!](#need-help-join-the-community) -- [Breaking changes](#breaking-changes) +- [Backward-incompatible changes](#backward-incompatible-changes) - [Farewell to the following](#farewell-to-the-following) - [All changes](#all-changes) @@ -565,7 +565,7 @@ Are you more into email? [Sign-up for our Building the Open Home Newsletter](/ne to get the latest news about features, things happening in our community and other news about building an Open Home; straight into your inbox. -## Breaking changes +## Backward-incompatible changes {% details "Demo" %} diff --git a/source/changelogs/core-2022.8.markdown b/source/changelogs/core-2022.8.markdown index 9be7269e7fa..683d9502260 100644 --- a/source/changelogs/core-2022.8.markdown +++ b/source/changelogs/core-2022.8.markdown @@ -435,7 +435,7 @@ For a summary in a more readable format: - Bump pymazda to 0.3.7 ([@bdr99] - [#75546]) ([mazda docs]) (dependency) - Hide inactive repairs issues ([@emontnemery] - [#75556]) ([repairs docs]) - Add sync methods for create/deleting issues in repairs ([@frenck] - [#75557]) ([repairs docs]) -- Update icons for breaking changes in MDI 7.0.96 ([@bramkragten] - [#75560]) ([huawei_lte docs]) ([icloud docs]) ([netgear docs]) (breaking-change) (noteworthy) +- Update icons for backward-incompatible changes in MDI 7.0.96 ([@bramkragten] - [#75560]) ([huawei_lte docs]) ([icloud docs]) ([netgear docs]) (breaking-change) (noteworthy) - Add websocket command recorder/import_statistics ([@titilambert] - [#73937]) ([recorder docs]) (noteworthy) - Improve http decorator typing ([@cdce8p] - [#75541]) ([http docs]) ([auth docs]) ([repairs docs]) - Deprecate U.S. Citizenship and Immigration Services (USCIS) integration ([@frenck] - [#75562]) ([uscis docs]) (deprecation) diff --git a/source/changelogs/core-2023.5.markdown b/source/changelogs/core-2023.5.markdown index 7b584236156..bdbe61e16b5 100644 --- a/source/changelogs/core-2023.5.markdown +++ b/source/changelogs/core-2023.5.markdown @@ -599,7 +599,7 @@ For a summary in a more readable format: - Fix unknown/unavailable source sensor in Filter entities ([@frenck] - [#92241]) - Bump plugwise to v0.31.1 ([@bouwew] - [#92249]) - Bump pyunifiprotect to 4.8.3 ([@bdraco] - [#92251]) -- Pin `pyasn1` and `pysnmplib` since `pyasn1` 0.5.0 has breaking changes and `pysnmp-pyasn1` and `pyasn1` are both using the `pyasn1` namespace ([@bdraco] - [#92254]) +- Pin `pyasn1` and `pysnmplib` since `pyasn1` 0.5.0 has backward-incompatible changes and `pysnmp-pyasn1` and `pyasn1` are both using the `pyasn1` namespace ([@bdraco] - [#92254]) - Handle onvif errors when detail is returned as bytes ([@bdraco] - [#92259]) - Add VoIP error tone ([@synesthesiam] - [#92260]) - Fix Google Mail Sensor key error ([@tkdrob] - [#92262])