jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-27 19:26:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

Breaking changes: rename to backward-incompatible (#29927)

Browse Source
This commit is contained in:
c0ffeeca7 2023-11-20 13:09:55 +01:00 committed by GitHub
parent b9cd70f635
commit 2a428bb239
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
148 changed files with 255 additions and 255 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
source/_includes/common-tasks/update.md
View File

@ -3,7 +3,7 @@
Best practice for updating a Home Assistant installation:
1. Backup your installation{% if page.installation == "os" or page.installation == "supervised" %}, using the backup functionality Home Assistant offers{% endif %}.
2. Check the release notes for breaking changes on [Home Assistant release notes](/blog/categories/core/). Be sure to check all release notes between the version you are running and the one you are upgrading to. Use the search function in your browser (`CTRL + f` / `CMD + f`) and search for **Breaking Changes**.
2. Check the release notes for backward-incompatible changes on [Home Assistant release notes](/blog/categories/core/). Be sure to check all release notes between the version you are running and the one you are upgrading to. Use the search function in your browser (`CTRL + f` / `CMD + f`) and search for **Backward-incompatible changes**.
{% if page.installation == "os" or page.installation == "supervised" %}
3. Select "Create backup before updating" in case you encounter an issue that requires a rollback.
4. Update Home Assistant.

2
source/_integrations/hassio.markdown
View File

@ -122,7 +122,7 @@ Write data to add-on stdin.
### Service hassio.addon_update
Update add-on. This service should be used with caution since add-on updates can contain breaking changes. It is highly recommended that you review release notes/change logs before updating an add-on.
Update add-on. This service should be used with caution since add-on updates can contain backward-incompatible changes. It is highly recommended that you review release notes/change logs before updating an add-on.
| Service Data Attribute | Optional | Description |
| ---------------------- | -------- | ----------- |

2
source/_posts/2015-10-26-firetv-and-radiotherm-now-supported.markdown
View File

@ -35,7 +35,7 @@ After two weeks of hard work I'm proud to announce the release of Home Assistant
<!--more-->
#### Breaking changes
#### Backward-incompatible changes
As part of this release we did some cleanup which introduced backwards incompatible changes:

2
source/_posts/2015-11-16-zwave-switches-lights-and-honeywell-thermostats-now-supported.markdown
View File

@ -19,7 +19,7 @@ homeassistant:
icon: "mdi:air-conditioner"
```
#### Breaking changes
#### Backward-incompatible changes
- Any existing zone icon will have to be replaced with one from [Material Design Icons].
- LimitlessLED light services require colors to be specified in RGB instead of XY.

2
source/_posts/2015-12-20-amazon-echo-icloud-and-templates.markdown
View File

@ -71,7 +71,7 @@ The temperature at home is {{ states('sensor.temperature') }}.
More information and examples can be found in the [template documentation][Template].
### Breaking changes
### Backward-incompatible changes
Templates will now be the only way to extract data from 'raw' sources like REST, CommandSensor or MQTT. This will replace any specific option that used to do this before. This means that `precision`, `factor`, `attribute` or `json_path` etc will no longer work.

2
source/_posts/2016-03-12-z-wave-pep257-templated-service-calls.markdown
View File

@ -49,7 +49,7 @@ automation:
{% endraw %}
### Breaking Changes
### Backward-incompatible changes
- Media Player: Attributes to call service play_media has been renamed to
`media_content_type` and `media_content_id`, to match the corresponding media

4
source/_posts/2016-03-26-embedded-mqtt-broker-uber-yamaha-growl.markdown
View File

@ -12,7 +12,7 @@ categories:
Party people, 0.16 is here! The big thing with this release is that we have completely removed the barrier to get started by MQTT by being able to launch an embedded MQTT server: [hbMQTT]. Just add `mqtt:` to your config and a broker is launched and connected with Home Assistant.
Further in this release a bunch of cool new stuff, bug fixes and rewrites for the Vera and Tellstick component (see breaking changes section at bottom for this!).
Further in this release a bunch of cool new stuff, bug fixes and rewrites for the Vera and Tellstick component (see backward-incompatible changes section at bottom for this!).
Rock on.
@ -65,7 +65,7 @@ Rock on.
[Z-Wave]: /integrations/zwave/#services
[Yamaha receivers]: /integrations/yamaha
### Breaking changes
### Backward-incompatible changes
- Automation: support for old deprecated config has been removed
- Tellstick configuration has changed

4
source/_posts/2016-04-09-onkyo-panasonic-gtfs-and-config-validation.markdown
View File

@ -51,6 +51,6 @@ Another big thing is the addition of GTFS support. You probably don't know it, b
[Raspberry PI]: /integrations/rpi_camera
[Z-Wave]: /integrations/zwave/#climate
### Breaking changes
### Backward-incompatible changes
As of now we are not aware of any breaking changes. However, it might be that Home Assistant will not start for you because of an invalid configuration. A common mistake that people are making is that they are still referring to `execute_service` in their script configs. This should be `service`.
As of now we are not aware of any backward-incompatible changes. However, it might be that Home Assistant will not start for you because of an invalid configuration. A common mistake that people are making is that they are still referring to `execute_service` in their script configs. This should be `service`.

4
source/_posts/2016-04-21-bluetooth-lg-webos-tvs-and-roombas.markdown
View File

@ -13,7 +13,7 @@ og_image: /images/blog/2016-04-release-18/social.png
It's time for 0.18. This release cycle is 2 days shorter than usual as I'll be traveling to Europe. This also means that it can take some more time before you get feedback on PRs.
Since the last release we have moved all Home Assistant source code etc into its own [organization on GitHub](https://github.com/home-assistant). We're growing up! This sadly did cause us to have to move all Docker images. Check the breaking changes section for more info.
Since the last release we have moved all Home Assistant source code etc into its own [organization on GitHub](https://github.com/home-assistant). We're growing up! This sadly did cause us to have to move all Docker images. Check the backward-incompatible changes section for more info.
<a href='/demo/'><img src='/images/blog/2016-04-release-18/media_player.png' style='box-shadow: none; border: 0;' /></a>
@ -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.

2
source/_posts/2016-05-21-release-020.markdown
View File

@ -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

2
source/_posts/2016-06-08-super-fast-web-enocean-lirc.markdown
View File

@ -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].

2
source/_posts/2016-07-01-envisalink-homematic-hdmi-cec-and-sony-bravia-tv.markdown
View File

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

2
source/_posts/2016-07-16-sqlalchemy-knx-join-simplisafe.markdown
View File

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

2
source/_posts/2016-07-30-custom-frontend-panels--jupyter-notebooks--directv.markdown
View File

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

2
source/_posts/2016-08-13-foursquare-fast-com-ffmpeg-gpsd.markdown
View File

@ -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:

4
source/_posts/2016-08-27-notifications-hue-fake-unification.markdown
View File

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

4
source/_posts/2016-09-10-notify-group-reload-api-pihole.markdown
View File

@ -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:

4
source/_posts/2016-09-29-async-sleepiq-emoncms-stocks.markdown
View File

@ -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`.

4
source/_posts/2016-10-08-hassbian-rest-digital-ocean.markdown
View File

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

2
source/_posts/2016-10-22-flash-briefing-updater-hacktoberfest.markdown
View File

@ -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]

2
source/_posts/2016-11-05-hacktoberfest-influxdb-weather.markdown
View File

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

2
source/_posts/2016-11-20-calendar--wink-thermostats--cisco-ios.markdown
View File

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

2
source/_posts/2016-12-03-remote-websockets-sonarr.markdown
View File

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

2
source/_posts/2017-01-14-iss-usps-images-packages.markdown
View File

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

4
source/_posts/2017-01-28-face-coffee-wink.markdown
View File

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

2
source/_posts/2017-02-11-alert-appletv-mqtt-yeelight.markdown
View File

@ -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`.

6
source/_posts/2017-02-25-config-panel-and-state-restoration.markdown
View File

@ -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

2
source/_posts/2017-03-11-repurpose-any-android-phone-as-ip-camera.markdown
View File

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

2
source/_posts/2017-03-25-todo-volumio-workday.markdown
View File

@ -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]).

2
source/_posts/2017-04-08-eddystone-beacons--lockitron-locks--total-connect.markdown
View File

@ -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])
<!--more-->
## 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`.

2
source/_posts/2017-04-22-ikea-tradfri--spotify.markdown
View File

@ -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)
<!--more-->
## 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])

2
source/_posts/2017-05-06-zigbee-opencv-dlib.markdown
View File

@ -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])
<!--more-->
## 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)

2
source/_posts/2017-05-20-automation-editor-zwave-panel-ocr.markdown
View File

@ -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)

2
source/_posts/2017-06-04-release-46.markdown
View File

@ -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)

2
source/_posts/2017-06-15-zwave-entity-ids.markdown
View File

@ -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

2
source/_posts/2017-06-17-release-47.markdown
View File

@ -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.
<!--more-->
## Breaking changes
## Backward-incompatible changes
- Update opencv config to match other image processors ([@Teagan42] - [#7864]) ([image_processing.opencv docs]) (breaking change)

2
source/_posts/2017-07-02-release-48.markdown
View File

@ -75,7 +75,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
<!--more-->
## 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)

2
source/_posts/2017-07-16-release-49.markdown
View File

@ -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.
<!--more-->
## 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)

2
source/_posts/2017-07-29-release-50.markdown
View File

@ -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.
<!--more-->
## 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)

2
source/_posts/2017-08-12-release-51.markdown
View File

@ -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.
<!--more-->
## 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)

2
source/_posts/2017-08-26-release-0-52.markdown
View File

@ -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.
<!--more-->
## 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)

2
source/_posts/2017-09-09-release-53.markdown
View File

@ -87,7 +87,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
<!--more-->
## 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:

2
source/_posts/2017-09-23-release-54.markdown
View File

@ -39,7 +39,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
<!--more-->
## Breaking Changes
## Backward-incompatible changes
- Sensor - OneWire: This update changes the names of the sensors from `<sensor_name>` to `<sensor_name> <Sensor_type>` ([@tcastberg] - [#9404]) ([sensor.onewire docs]) (breaking change)
- Renamed Xiaomi platforms to include their protocol names. xiaomi -> xiaomi_aqara, xiaomi_aqara.switch, xiaomi_aqara.light, xiaomi_aqara.binary_sensor, ... and vacuum.xiaomi, xiaomi_philipslight -> xiaomi_miio, vacuum.xiaomi_miio, light.xiaomi_miio ([@danielhiversen] - [#9426]) (breaking change)

2
source/_posts/2017-10-07-release-55.markdown
View File

@ -61,7 +61,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
<!--more-->
## Breaking Changes
## Backward-incompatible changes
- history_graph component: If your component used `history.get_significant_states` function then you need to adjust the string `entity_id` parameter has been changed to a list of strings `entity_ids` parameter. ([@andrey-git] - [#9472]) (breaking change)
- UPNP component: The `external_port` configuration option was removed. ([@balloob] - [#9560]) ([upnp docs]) (breaking change)

2
source/_posts/2017-10-21-release-56.markdown
View File

@ -75,7 +75,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
<!--more-->
## Breaking Changes
## Backward-incompatible changes
- Simplify track_same_state ([@balloob] - [#9795]) ([automation.numeric_state docs]) ([automation.state docs]) ([binary_sensor.template docs]) (breaking change)
- Split map panel out into its own component ([@cgarwood] - [#9814]) ([map docs]) (breaking change) (new-platform)

4
source/_posts/2017-11-04-release-57.markdown
View File

@ -44,7 +44,7 @@ This means that we processed over 20 Pull requests per day. The result was alrea
## IKEA TRÅDFRI
Good news and bad news on this front. The bad news is that IKEA changed the internal API for TRÅDFRI with a firmware update, breaking the Home Assistant integration. The good news is that they were nice enough to [email us with instructions on the breaking changes][ikea email].
Good news and bad news on this front. The bad news is that IKEA changed the internal API for TRÅDFRI with a firmware update, breaking the Home Assistant integration. The good news is that they were nice enough to [email us with instructions on the backward-incompatible changes][ikea email].
Long time contributor [@lwis] jumped on the case and managed to migrate our integration in Home Assistant in time for this release. Great work!
@ -107,7 +107,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
<!--more-->
## Breaking Changes
## Backward-incompatible changes
- IKEA TRÅDFRI: We no longer support entering the key in the configuration. ([@lwis] - [#10282]) ([tradfri docs]) (breaking change)
- API.AI was renamed to [Dialogflow](/integrations/dialogflow/). This requires to rename the entry in your `configuration.yaml` file from `apiai:` to `dialogflow`. ([@fabaff] - [#10006]) ([dialogflow docs]) (breaking change)

2
source/_posts/2017-11-18-release-58.markdown
View File

@ -80,7 +80,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
<!--more-->
## Breaking Changes
## Backward-incompatible changes
- `hass.states.is_state_attr(entity_id, attribute, value)` has been removed. The template version still exists. Unused method parameter `wait` has been removed from `hass.bus.async_fire` ([@balloob] - [#10305]) (breaking change)
- Refactor Neato botvac components as a vacuum ([@jabesq] - [#9946]) ([neato docs]) ([switch.neato docs]) ([vacuum.neato docs]) (breaking change) (new-platform)

2
source/_posts/2017-12-03-release-59.markdown
View File

@ -79,7 +79,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
<!--more-->
## Breaking Changes
## Backward-incompatible changes
- Added cycles config option to LaMetric notifications ([@frittes] - [#10656]) ([notify.lametric docs]) (breaking change)
- Fix name collision when using multiple Hue bridges ([@zBart] - [#10486]) ([light.hue docs]) (breaking change)

2
source/_posts/2017-12-17-release-60.markdown
View File

@ -71,7 +71,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
<!--more-->
## Breaking Changes
## Backward-incompatible changes
- Update snips to listen on new mqtt topic and utilize rawValue ([@tschmidty69] - [#11020]) ([snips docs]) (breaking change)
- Refactor hue to split bridge support from light platform ([@andreacampi] - [#10691]) ([hue docs]) ([light.hue docs]) (breaking change) (new-platform)

8
source/_posts/2018-01-14-release-61.markdown
View File

@ -1,6 +1,6 @@
---
title: "0.61: Coinbase, Discogs, iGlo, Sochain"
description: "New crypto currency sensors and other new stuff including breaking changes."
description: "New crypto currency sensors and other new stuff including backward-incompatible changes."
date: 2018-01-14 18:00:00
date_formatted: "January 14, 2018"
author: Fabian Affolter
@ -15,11 +15,11 @@ og_image: /images/blog/2018-01-0.61/components.png
Almost a 100 contributors to this release 🎉 That's what you get when you skip a release. It's a little late but "Happy New Year" and welcome to 0.61 the first release 2018.
This release contain some breaking changes. Please make sure that you check the section below if you are running into trouble.
This release contain some backward-incompatible changes. Please make sure that you check the section below if you are running into trouble.
## Assistant configs
We made a mistake in the foundation of both the Google Assistant and Alexa integrations: they were storing their config inside customize. This is not the right place and we moved them to be under the components itself. See the breaking changes section on how to migrate.
We made a mistake in the foundation of both the Google Assistant and Alexa integrations: they were storing their config inside customize. This is not the right place and we moved them to be under the components itself. See the backward-incompatible changes section on how to migrate.
## Hass.io updates
@ -73,7 +73,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
<!--more-->
## Breaking Changes
## Backward-incompatible changes
- Extend Threshold binary sensor to support ranges. This means that you can now set `up` and `lower`. ([@DanNixon] - [#11110]) ([binary_sensor.threshold docs]) (breaking change)
- The Steam game platform contains changes:

2
source/_posts/2018-01-27-release-62.markdown
View File

@ -49,7 +49,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
<!--more-->
## Breaking Changes
## Backward-incompatible changes
- Tahoma platform will get new entity IDs ([@glpatcern] - [#11547]) ([tahoma docs]) ([cover.tahoma docs]) (breaking change)
- Mold indicator: attribute names no longer include spaces or periods ([@olskar] - [#11694]) ([sensor.mold_indicator docs]) (breaking change)

2
source/_posts/2018-02-10-release-63.markdown
View File

@ -79,7 +79,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
<!--more-->
## Breaking Changes
## Backward-incompatible changes
- updated sensor name ([@philklei] - [#12084]) ([sensor.tahoma docs]) (breaking change)
- Originally Canary camera is added per location and only displays an image that was captured due to motion. Now it is per device (each location can have multiple devices) with live stream support. ([@snjoetw] - [#11949]) ([canary docs]) ([camera.canary docs]) (breaking change)

2
source/_posts/2018-02-26-release-64.markdown
View File

@ -111,7 +111,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
<!--more-->
## Breaking Changes
## Backward-incompatible changes
- Home Assistant now defaults to purge recorded history that is older than 10 days. If you want to keep your recorded data for longer than that, you must configure the number of days to retain _before starting 0.64 for the first time_, for example:
```yaml

2
source/_posts/2018-03-09-release-65.markdown
View File

@ -178,7 +178,7 @@ intent_script:
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.
<!--more-->
## Breaking Changes
## Backward-incompatible changes
- Insteon PLM: If you have created platform overrides in your configuration.yaml file to change a your INSTEON device to map to a different Home Assistant platform, that mapping will no longer be in effect. Please see the new device override capabilities in the [insteon_plm documentation](/integrations/insteon/). ([@teharris1] - [#12534]) ([insteon_plm docs]) ([binary_sensor.insteon_plm docs]) ([fan.insteon_plm docs]) ([light.insteon_plm docs]) ([sensor.insteon_plm docs]) ([switch.insteon_plm docs]) (breaking change)
- AirVisual's air index unit is AQI (Air Quality Index), not PSI (Pressure per Square Inch). ([@chilicheech] - [#12730]) ([sensor.airvisual docs]) (breaking change)

2
source/_posts/2018-03-30-release-66.markdown
View File

@ -52,7 +52,7 @@ A quick note if you are using Philips Hue and a Hue custom component: it will no
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.
<!--more-->
## Breaking Changes
## Backward-incompatible changes
- Refactor Hue: If you specify a bridge in your config, the `host` key is now required and needs to be a valid IP address. Option `allow_in_emulated_hue` has been removed. Exclude the lights via the emulated hue config. Due to the internal changes of how the Hue integration works, any Hue custom component will no longer work. ([@balloob] - [#13043]) ([hue docs]) ([light.hue docs]) (breaking change)
- Z-Wave: In version 0.47, the opt-in `new_entity_ids` configuration was added to Z-Wave to smooth the transition through the change. Support for old entity IDs is now removed, and the configuration is no longer necessary. If you are migrating from 0.63 or higher, your entity IDs will already be stored in the Entity Registry and no changes are required. If not, entity IDs can now be manually configured using the Entity Registry if necessary. ([@armills] - [#12652]) ([zwave docs]) (breaking change)

2
source/_posts/2018-04-14-release-67.markdown
View File

@ -54,7 +54,7 @@ This release includes a security fix. The error log was accessible via the API w
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.
<!--more-->
## Breaking Changes
## Backward-incompatible changes
- Updates default Pilight port number ([@frenck] - [#13419]) ([pilight docs]) (breaking change)
- Update to new "b2vapi" of BMW ConnectedDrive ([@ChristianKuehnel] - [#13305]) ([bmw_connected_drive docs]) ([binary_sensor.bmw_connected_drive docs]) ([lock.bmw_connected_drive docs]) ([sensor.bmw_connected_drive docs]) (breaking change)

2
source/_posts/2018-04-27-release-68.markdown
View File

@ -60,7 +60,7 @@ Another cool new platform, also by [@mjg59], is support for Eufy devices. Eufy i
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.
<!--more-->
## Breaking Changes
## Backward-incompatible changes
- Icons! Material Design Icons has implemented some naming guidelines and this caused 9 icons to change names, 3 of which are home automation icons: `roomba` -> `robot-vacuum`, `nest-protect` -> `smoke-detector`, `nest-thermostat` -> `thermostat` ([see all changes](http://templarian.com/2018/04/18/material-design-icons-v2-3-54/)).
- Support for multiple MAX!Cube LAN gateways caused a slight change to the configuration schema. Make sure to check the docs for the new one. ([@syssi] - [#13517]) ([maxcube docs]) ([binary_sensor.maxcube docs]) ([climate.maxcube docs]) (breaking change)

2
source/_posts/2018-05-11-release-69.markdown
View File

@ -37,7 +37,7 @@ Not much time to write a great intro this time as we're hanging out at PyCon! So
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.
<!--more-->
## Breaking Changes
## Backward-incompatible changes
- Pollen.com: Added attributes on top 3 allergens. This caused attribute names `primary_allergen_genus`, `primary_allergen_name` and `primary_allergen_type` to be suffixed with `_1` ([@bachya] - [#14018]) ([sensor.pollen docs]) (breaking change)
- Add Sonos device attribute with grouping information. The `media_player.sonos` attribute `is_coordinator` has been removed; the new attribute `sonos_group` (listing all group members, coordinator first) can be used instead. ([@amelchio] - [#13553]) ([media_player.sonos docs]) (breaking change)

2
source/_posts/2018-05-18-release-70.markdown
View File

@ -53,7 +53,7 @@ Another cool one this release is [Facebox][image_processing.facebox docs]. It wi
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.
<!--more-->
## Breaking Changes
## Backward-incompatible changes
- Converted SABnzbd to a component. Set it up using the new config:
```yaml

2
source/_posts/2018-06-10-release-71.markdown
View File

@ -53,7 +53,7 @@ Have a good weekend everyone!
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.
<!--more-->
## Breaking Changes
## Backward-incompatible changes
- BOM sensor: `'Wind Direction kt'` to `'Wind Speed kt'` (fixes #14535) ([@fabaff] - [#14541]) (breaking change)
- Removed attribute current_time from Raincloudy sensors to avoid being triggered by recorder component ([@tchellomello] - [#14584]) ([raincloud docs]) ([switch.raincloud docs]) (breaking change)

2
source/_posts/2018-06-22-release-72.markdown
View File

@ -73,7 +73,7 @@ Enjoy this release and have a good weekend all!
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.
<!--more-->
## Breaking Changes
## Backward-incompatible changes
- For developers of custom panel: Remove ability to register panels directly with the frontend component. Register with custom panel component instead. ([@balloob] - [#14805]) ([frontend docs]) (breaking change)
- Rename Hive hub friendly name to include "Hive" name ([@SteveEdson] - [#14747]) ([sensor.hive docs]) (breaking change)

2
source/_posts/2018-07-06-release-73.markdown
View File

@ -40,7 +40,7 @@ And last but not least, [@Klikini] has upgraded Rachio support from cloud pollin
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.
<!--more-->
## Breaking Changes
## Backward-incompatible changes
- The `pi_hole` sensor is now limited to `ads_blocked_today` by default and will no longer show all available data. Use [`monitored_conditions`](/integrations/pi_hole#monitored_conditions) to list the sensors you want. ([@fabaff] - [#15014]) ([sensor.pi_hole docs]) (breaking change)
- Update PostNL unit of measure to `packages` to align with UPS ([@keesschollaart81] - [#15023]) (breaking change)

2
source/_posts/2018-07-21-release-74.markdown
View File

@ -63,7 +63,7 @@ I'm happy to announce that this release introduces support for Tuya thanks to [@
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.
<!--more-->
## Breaking Changes
## Backward-incompatible changes
- Fixer.io has changed their API and now requires an API key. (fixes #14911) ([@fabaff] - [#15279]) ([sensor.fixer docs]) (breaking change)
- Add support to use HTTPS URLs to SynologyDSM and make it the default ([@tchellomello] - [#15270]) ([sensor.synologydsm docs]) (breaking change)

2
source/_posts/2018-08-03-release-75.markdown
View File

@ -66,7 +66,7 @@ This release also includes a bunch more Tuya integrations thanks to [@huangyupen
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.
<!--more-->
## Breaking Changes
## Backward-incompatible changes
- Moon sensor states are now lowercase with underscores instead of spaces, allowing it to be translated in the frontend. ([@pvizeli] - [#15498]) ([sensor.moon docs]) (breaking change)
- Insteon Mini-Remote now emit events instead of show as a binary sensor ([@teharris1] - [#15523]) ([insteon_plm docs]) ([binary_sensor.insteon_plm docs]) ([switch.insteon_plm docs]) (breaking change)

4
source/_posts/2018-08-17-release-76.markdown
View File

@ -88,14 +88,14 @@ Experiencing issues introduced by this release? Please report them in our [issue
<!--more-->
## Breaking Changes
## Backward-incompatible changes
- Keenetic NDMS: user needs to have access to the TelNet interface ([@foxel] - [#15511]) ([device_tracker docs]) (breaking change)
- openweathermap: wind speed is now correctly in km/h (fixes #15710) ([@fabaff] - [#15740]) ([weather.openweathermap docs]) (breaking change)
- Remove Telstra notifiy component: This API has been decommissioned on the 31st of May 2018 by Telstra ([@dgomes] - [#15757]) ([notify docs]) (breaking change)
- deCONZ - support for power plugs. Power plugs that are of type "On/Off plug-in unit" and "Smart plug" (Osram and Innr among others) will now be switches instead of lights. Entities will be found as switch.entity_id instead of light.entity_id. ([@Kane610] - [#15752]) ([deconz docs]) ([light.deconz docs]) ([switch.deconz docs]) (breaking change) (new-platform)
- HTTP: Make sure use_x_forward_for and trusted_proxies must be configured together ([@awarecan] - [#15804]) ([http docs]) (breaking change)
- Velbus: Breaking changes include auto-discovery support so that you don't need to specify modules manually anymore in the configuration file, but just load the velbus component which will automatically load the switch and binary_sensor platforms. In addition, the fan and light platforms are removed since these should be modeled with template platform based on velbus switches. ([@thomasdelaet] - [#13742]) ([velbus docs]) ([binary_sensor.velbus docs]) ([switch.velbus docs]) (breaking change)
- Velbus: Backward-incompatible changes include auto-discovery support so that you don't need to specify modules manually anymore in the configuration file, but just load the velbus component which will automatically load the switch and binary_sensor platforms. In addition, the fan and light platforms are removed since these should be modeled with template platform based on velbus switches. ([@thomasdelaet] - [#13742]) ([velbus docs]) ([binary_sensor.velbus docs]) ([switch.velbus docs]) (breaking change)
- Facebox: Events are no longer fired when a face is taught, as these are unnecessary and the info they convey is already in the logs. ([@robmarkcole] - [#15439]) ([image_processing.facebox docs]) (breaking change)
- AMCrest switch: Fix for multiple camera switches naming of entity. May change switch entity_id. Please check your automation and update the identity-id if you have previously assigned a name to your camera as it appends the name of the camera to the switch id. ([@rafale77] - [#14028]) ([switch.amcrest docs]) (breaking change)
- MQTT embedded broker will no longer rely on HTTP API password to automatically configure itself. You need to set own password. ([@awarecan] - [#15929]) ([mqtt docs]) (breaking change) (beta fix)

2
source/_posts/2018-08-29-release-77.markdown
View File

@ -103,7 +103,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
<!--more-->
## Breaking Changes
## Backward-incompatible changes
- Enable auth by default 🙈. It is no longer possible to access Home Assistant without authentication ([@balloob] - [#16107]) (breaking change)
- It's no longer possible to use a trusted network to connect to the websocket API. You need to get a token and use that to connect. ([@awarecan] - [#15812]) ([auth docs]) ([http docs]) ([websocket_api docs]) (breaking change)

2
source/_posts/2018-09-15-release-78.markdown
View File

@ -72,7 +72,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
<!--more-->
## Breaking Changes
## Backward-incompatible changes
- Trafikverket weather: Instead of having multiple sensor configurations per station, add only one configuration per station and select the type of measurement data to subscribe to using monitored_conditions.
The configuration value type should no longer be used. ([@endor-force] - [#15935]) ([sensor.trafikverket_weatherstation docs]) (breaking change)

2
source/_posts/2018-10-01-release-79.markdown
View File

@ -111,7 +111,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
<!--more-->
## Breaking Changes
## Backward-incompatible changes
- Netdata configuration change: Allows multiple elements per group. Specify the `data_group` as part of the sensor description. See docs for details. ([@reefab] - [#16656]) ([sensor.netdata docs]) (breaking change)
- The Dyson sensor Air Quality Index is now named AQI following Dyson's mobile app ([@glpatcern] - [#14550]) ([sensor.dyson docs]) (breaking change)

2
source/_posts/2018-10-12-release-80.markdown
View File

@ -117,7 +117,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
<!--more-->
## Breaking Changes
## Backward-incompatible changes
- Add additional Netatmo public data sensors ([@GP8x] - [#16671]) ([netatmo docs]) ([sensor.netatmo_public docs]) (breaking change)
- Developers only: we have removed all service helpers (like turn_on method in light coponent), as they werent used. ([@cdce8p] - [#16832], [#16879], [#16863], [#16892], [#16920], [#17038], [#17055], [#16917])

2
source/_posts/2018-10-29-release-81.markdown
View File

@ -141,7 +141,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
<!--more-->
## Breaking Changes
## Backward-incompatible changes
- LIFX can now be configured from the integrations page in the config panel and advanced configuration is available through the `lifx:` component configuration. Configuring LIFX via light platform config no longer works. ([@amelchio] - [#17201]) ([lifx docs]) ([light.lifx docs]) (breaking change)
- Daikin Climate now follows the official operating modes, making it compatible with Google Assistant, Alexa and HomeKit. ([@MatteGary] - [#16913]) ([climate.daikin docs]) (breaking change)

2
source/_posts/2018-11-08-release-82.markdown
View File

@ -89,7 +89,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
<!--more-->
## Breaking Changes
## Backward-incompatible changes
- Migrate Mailgun to use the webhook component ([@rohankapoorcom] - [#17464]) ([ifttt docs]) ([mailgun docs]) ([notify docs]) ([automation.webhook docs]) (breaking change)
- Migrate twilio webhooks to the webhook component ([@rohankapoorcom] - [#17715]) ([twilio docs]) (breaking change)

2
source/_posts/2018-11-28-release-83.markdown
View File

@ -159,7 +159,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
<!--more-->
## Breaking Changes
## Backward-incompatible changes
- OwnTracks is now using config entries. To set it up, go to the configuration panel and configure it there. When configured and MQTT is available, will automatically listen there too. **You must remove the old device tracker before upgrading** ([@kirichkov] - [#17034]) ([@balloob] - [#18759]) ([owntracks docs]) (breaking change)
- Removes melissa sensors (they should be state attributes as implemented in #18201) ([@kennedyshead] - [#18214]) ([melissa docs]) (breaking change)

4
source/_posts/2018-12-12-release-84.markdown
View File

@ -47,7 +47,7 @@ So if you were using Lovelace before 0.84, you now have two options. Option one
If you want to continue managing a YAML file, [check here how to enable the YAML mode](/dashboards/yaml-mode/). The file `ui-lovelace.yaml` will now follow the same options as `configuration.yaml`. This means that the Lovelace YAML config is now parsed with YAML 1.1 instead of YAML 1.2. Major change is that you need to make sure that you wrap `on` and `off` with quotes in your configs!
We have also aligned the configuration of all the cards, causing breaking changes. Changes are especially focused around how we define actions for short and long presses. See [the docs](/dashboards/changelog/) for more info.
We have also aligned the configuration of all the cards, causing backward-incompatible changes. Changes are especially focused around how we define actions for short and long presses. See [the docs](/dashboards/changelog/) for more info.
Editor UI is now further processed. You can manage your Lovelace UI without leaving your browser! It is possible to add, edit and delete views. It is possible to add, edit, move and delete cards, including custom cards!
@ -177,7 +177,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
<!--more-->
## Breaking Changes
## Backward-incompatible changes
- State restoration will not work the first time you start 0.84. ([@armills] - [#17270]) ([history docs])
- Support for multiple IHC controllers added. Manual IHC device configuration must be moved from platform sections to controller configuration section under the ihc component section. ([@mopolus] - [#18058]) ([ihc docs]) ([binary_sensor.ihc docs]) ([light.ihc docs]) ([switch.ihc docs]) (breaking change)

2
source/_posts/2019-01-09-release-85.markdown
View File

@ -78,7 +78,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
<!--more-->
## Breaking Changes
## Backward-incompatible changes
- Targeting all entities in a domain by not sending an entity_id to a service is now deprecated. Instead, send `entity_id: all` if you want to target all. The old method will work for a couple of releases more, but will print a warning. Please migrate. ([@balloob] - [#19006]) (breaking change)
- The default interval of the weather component was aligned with the sensor component and is now 30 seconds instead of 15 seconds. ([@fabaff] - [#19186]) ([weather docs]) (breaking change)

6
source/_posts/2019-01-23-release-86.markdown
View File

@ -36,11 +36,11 @@ The Zigbee team is also planning a bunch of cool things for 2019. Direct device
Screenshot of the Zigbee management panel.
</p>
## Noteworthy breaking changes
## Noteworthy backward-incompatible changes
Update: the entity ID one was too harsh, it's now a warning.
This release also includes two noteworthy breaking changes. One is a follow-up on the slugify breaking change from last release. We did not update the validation check for config options that need to be valid slugs. This means that some of your config values might be invalid. Keep an eye at the console as we have a new message to tell you which ones are wrong.
This release also includes two noteworthy backward-incompatible changes. One is a follow-up on the slugify breaking change from last release. We did not update the validation check for config options that need to be valid slugs. This means that some of your config values might be invalid. Keep an eye at the console as we have a new message to tell you which ones are wrong.
The following things are not allowed in entity IDs:
@ -126,7 +126,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
<!--more-->
## Breaking Changes
## Backward-incompatible changes
- Automation: Split time_pattern triggers from time trigger ([@armills] - [#19825]) ([automation.interval docs]) ([automation.time docs]) (breaking change)
- Each instance of Home Assistant will now generate it's own unique webhook url for Geofencyto use. One will need to be generated and provided to the iOS app to replace the existing url: `https://myhome.duckdns.org/api/geofency?api_password=HA_PASSWORD` ([@rohankapoorcom] - [#18951]) ([geofency docs]) (breaking change)

2
source/_posts/2019-02-06-release-87.markdown
View File

@ -92,7 +92,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
<!--more-->
## Breaking Changes
## Backward-incompatible changes
- SolarEdge sensors: This PR changes the **entity names** of this sensor and the **monitoring condition keys** in the configuration: `sensor.solaredge_current_power` -> `sensor.solaredge_current_power`, `sensor.solaredge_last_day_data` -> `sensor.solaredge_energy_today`, `sensor.solaredge_last_month_data` -> `sensor.solaredge_energy_this_month`, `sensor.solaredge_last_year_data` -> `sensor.solaredge_energy_this_year`, `sensor.solaredge_life_time_data` -> `sensor.solaredge_lifetime_energy`, ([@LouisMT] - [#20109]) ([sensor.solaredge docs]) (breaking change)
- Geolocation is no longer creating a default group. ([@exxamalte] - [#20338]) ([geo_location docs]) (breaking change)

4
source/_posts/2019-02-20-release-88.markdown
View File

@ -25,7 +25,7 @@ We also have a new command line auth provider. This will allow you to use a shel
[@andrewsayre] has been working hard on extending the SmartThings support. This release brings sensors and climate devices into the mix. Awesome!
## Noteworthy breaking changes
## Noteworthy backward-incompatible changes
We have tightened config validation, so expect a couple of new warnings. Platform configuration will no longer allow to contain keys that are not supported. This should help with finding typos in your current and future YAML configs. This will currently fallback to a warning and will become a full error in the future.
@ -130,7 +130,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
<!--more-->
## Breaking Changes
## Backward-incompatible changes
- Split googlehome to a component with device tracker platform ([@ludeeus] - [#19971]) ([device_tracker docs]) ([googlehome docs]) (breaking change) (new-platform)
- Support for new velux api, added cover.velux ([@Julius2342] - [#18738]) ([velux docs]) ([cover.velux docs]) (breaking change) (new-feature) (new-platform)

6
source/_posts/2019-03-13-release-89.markdown
View File

@ -17,7 +17,7 @@ It's time for release 0.89. It's another great new release with some cool new fe
This release introduces a new mobile app component. [@robbiet480], who also works on the iOS app, has taken the best parts of the Home Assistant iOS app component and turned it into a standardized API that any mobile app can build upon. This will allow any mobile apps to integrate with Home Assistant with a great user experience. If you are a mobile app developer, please check the updated [app integration docs](https://developers.home-assistant.io/docs/api/native-app-integration/). We will be fine tuning the API in upcoming releases. Feedback is welcome.
## Noteworthy Breaking Changes
## Noteworthy backward-incompatible changes
__Custom Components file structure change:__ A significant change in how the "under the hood" of Home Assistant works has led to forcing platforms to be resolved based off the component path, if it exists.
@ -121,7 +121,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
<!--more-->
## Breaking Changes
## Backward-incompatible changes
- __HomeMatic component's wireless actors__ are having two RSSI values. The way the component was programmed one of them was being overwritten. With this new change, the __`rssi` attribute of HomeMatic entities has been removed.__ As a replacement the attributes rssi_device and rssi_peer have been added. The attribute of `rssi` will no longer be available, you'll need to __update to `rssi_device`,__ and you can add `rssi_peer` now as well! (fixes #20900) ([@dagobert] - [#20902]) ([homematic docs]) (breaking change)
- You can now specifiy an action when calling the __yeelight_start_flow service__ on your yeelights. The __default action will be 'recover'__ if you do not specify something else. This action will be taken after the flow stops. ([@zewelor] - [#21195]) ([light.yeelight docs]) (breaking change)
@ -133,7 +133,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
- Add ADB server functionality to __Fire TV.__ This change __removes the `get_source`__ configuration option. ([@JeffLIrion] - [#21221]) ([media_player.firetv docs]) (breaking change)
- With the addition of the __SmartThings Cover__ platform, the SmartThings __Sensor platform will no longer represent Door, Garage Door and Window Share attributes.__ Additionally, if the cover device reports battery status, the value will be present as a __state attribute__ (battery_level) and not a discrete sensor. ([@andrewsayre] - [#21192]) ([cover docs]) ([smartthings docs]) (breaking change) (new-platform)
- The __Toon component__ was broken some time ago, so now requires a Toon API developer account and __can be configured using the Home Assistant integrations.__ Support for Switches & Smoke detectors has been removed. ([@frenck] - [#21186]) ([toon docs]) (breaking change) (new-platform)
- Addition of config for __trusted networks auth provider.__ It is a breaking changes for users who __manually configured__ trusted network auth provider. An invalid config error will be thrown and HA won't be able to fully started. (It is NOT a breaking changes for user who didn't manual configured trusted network auth provider.) ([@awarecan] - [#21111]) (breaking change)
- Addition of config for __trusted networks auth provider.__ It is a backward-incompatible changes for users who __manually configured__ trusted network auth provider. An invalid config error will be thrown and HA won't be able to fully started. (It is NOT a backward-incompatible changes for user who didn't manual configured trusted network auth provider.) ([@awarecan] - [#21111]) (breaking change)
- For some __HomeMatic devices the `sabotage` attribute is replaced by `error`.__ The value (if not 0) is a device specific error code. ([@dagobert] - [#21009]) ([homematic docs]) (breaking change)
## Beta Fixes

2
source/_posts/2019-03-20-release-90.markdown
View File

@ -138,7 +138,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
<!--more-->
## Breaking Changes
## Backward-incompatible changes
- __http.api_password__ - __Deprecated__ - Users who are still using api_password for authentication will need to move its configuration under auth_providers. Please see the [updated documentation](/docs/authentication/providers/#legacy-api-password) for further details. Those who don't make this change will see an INFO level reminder in the Home Assistant logs until the fix is made for a time, but please note, __api_password authentication will eventually be removed completely__ and we advise users to change to use one of the [other authentication methods](/docs/authentication/providers/#available-auth-providers). If you manually specify auth providers in your `configuration.yaml`, you will need to migrate your API Password from the http section to the auth provider section to continue using it. ([@awarecan] - [#21884]) ([api docs]) ([frontend docs]) ([hassio docs]) ([http docs]) ([mqtt docs]) ([websocket_api docs]) ([zeroconf docs]) ([camera.proxy docs])
- __Default Config__ - Default config no longer contains the discovery component. That is now part of the initial written configuration.yaml. If you rely on default config and want to use discovery, add `discovery:` back to your configuration.yaml.

2
source/_posts/2019-04-03-release-91.markdown
View File

@ -196,7 +196,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
<!--more-->
## Breaking Changes
## Backward-incompatible changes
- __Z-Wave__ - The usb_path in configuration.yaml now overrides config entry usb_path. This is potentially a breaking change if people have a stale usb_path setting in configuration.yaml that's no longer accurate. This should help reduce the number of people that need to manually edit the storage/core.config_entries file if their usb_path changes. ([@cgarwood] - [#22038]) ([zwave docs])

2
source/_posts/2019-04-24-release-92.markdown
View File

@ -167,7 +167,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
<!--more-->
## Breaking Changes
## Backward-incompatible changes
- __Google Assistant__ - You will now have to say a pin code before being able to control locks, doors and garage doors. You can set this pin in configuration -> cloud or, for manual installs, add `secure_devices_pin` to your config. ([@balloob] - [#23223]) ([cloud docs]) ([google_assistant docs]) (breaking change) (beta fix)
- __Google Assistant__ - Migrate light setting trait to use HSV color spectrum. If you have lights with colors, please run a Google Assistant SYNC after you update to this version. It will result in improved color representation. ([@balloob] - [#22980]) ([google_assistant docs])

4
source/_posts/2019-05-16-release-93.markdown
View File

@ -153,7 +153,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
<!--more-->
## Breaking Changes
## Backward-incompatible changes
- __Homematic IP Cloud__ - Adds homematicip cloud temperature sensor from thermostats. Entity IDs of HmIP-SLO (Light Sensor Outdoor) will change and stale entities will need to be removed from the entity registry. ([@SukramJ] - [#23263]) ([homematicip_cloud docs])
- __Pollen.com__
@ -368,7 +368,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
- Update docstrings ([@fabaff] - [#23624]) ([panasonic_bluray docs])
- Order imports ([@fabaff] - [#23623]) ([opple docs])
- Polling is default ([@fabaff] - [#23622]) ([serial_pm docs])
- Loosen discovery config validation to avoid breaking changes ([@Jc2k] - [#23625]) ([discovery docs])
- Loosen discovery config validation to avoid backward-incompatible changes ([@Jc2k] - [#23625]) ([discovery docs])
- Clean up redundant same-package ..package imports ([@scop] - [#23587]) ([greeneye_monitor docs]) ([huawei_lte docs]) ([tplink_lte docs])
- Upgrade pytest to 4.4.1 ([@scop] - [#23584])
- Upgrade mypy ([@scop] - [#23586])

2
source/_posts/2019-06-05-release-94.markdown
View File

@ -184,7 +184,7 @@ Because of this, we changed how packages are installed when running Home Assista
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
- __Sun__ - Inspired by a [reddit](https://www.reddit.com/r/homeassistant/comments/bm62hl/sunsun_chatty_sensor_psa/) report, the sun.sun sensor has been tuned so that it doesn't update nearly as frequently. Previously the sun.sun sensor was updating every 30 seconds, day and night. Now it updates dependent on the solar elevation. This could possibly be a breaking change for some users as it updates less frequently. ([@Swamp-Ig] - [#23832]) ([sun docs])
- __Doorbird__ -_Refactored_- This change cleans up the code for the component quite a bit. Schedule manipulation has been removed and HTTP views have been consolidated. The configuration changes should result in an overall easier experience for setting up a Doorbird in HA and allow for new Doorbird events to be utilized without having to update the component as often. No changes for switches or camera integrations of this component. ([@oblogic7] - [#23892]) ([doorbird docs])

4
source/_posts/2019-06-26-release-95.markdown
View File

@ -66,7 +66,7 @@ However, we didn't stop there. The [manual installations of Alexa](/integrations
<blockquote class="twitter-tweet"><p lang="en" dir="ltr">Released `v3.7.95` to NPM/CDN. 100 new icons! 🧙‍♂️ Preview: <a href="https://t.co/N02X3rnQ8N">https://t.co/N02X3rnQ8N</a> Read more: <a href="https://t.co/CHQ3TEdVM2">https://t.co/CHQ3TEdVM2</a> <a href="https://twitter.com/hashtag/MaterialDesign?src=hash&amp;ref_src=twsrc%5Etfw">#MaterialDesign</a> <a href="https://twitter.com/hashtag/OpenSource?src=hash&amp;ref_src=twsrc%5Etfw">#OpenSource</a> <a href="https://t.co/LlWy8RfFVu">pic.twitter.com/LlWy8RfFVu</a></p>&mdash; Material Icons (@MaterialIcons) <a href="https://twitter.com/MaterialIcons/status/1142474126004760576?ref_src=twsrc%5Etfw">June 22, 2019</a>
</blockquote>
## 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
<!--more-->
## 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)

2
source/_posts/2019-07-17-release-96.markdown
View File

@ -272,7 +272,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
<!--more-->
## 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])

2
source/_posts/2019-08-07-release-97.markdown
View File

@ -145,7 +145,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
<!--more-->
## 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])

4
source/_posts/2019-08-28-release-98.markdown
View File

@ -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
<!--more-->
## Breaking Changes
## Backward-incompatible changes
- **Deprecated**

4
source/_posts/2019-09-18-release-99.markdown
View File

@ -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.
<blockquote class="twitter-tweet"><p lang="en" dir="ltr">It&#39;s finally here. 🎉<br><br>Home Panel v2.0.0 is now released and has been completely rewritten in <a href="https://twitter.com/hashtag/React?src=hash&amp;ref_src=twsrc%5Etfw">#React</a> with <a href="https://twitter.com/hashtag/TypeScript?src=hash&amp;ref_src=twsrc%5Etfw">#TypeScript</a><br><br>⚠️Please read the release notes before upgrading as are breaking changes to know about before upgrading!<a href="https://t.co/NMDQu4zZW8">https://t.co/NMDQu4zZW8</a><a href="https://twitter.com/hashtag/HomePanel?src=hash&amp;ref_src=twsrc%5Etfw">#HomePanel</a> <a href="https://twitter.com/hashtag/HomeAssistant?src=hash&amp;ref_src=twsrc%5Etfw">#HomeAssistant</a> <a href="https://t.co/ucA1HxwurB">pic.twitter.com/ucA1HxwurB</a></p>&mdash; Timmo (@timmo001) <a href="https://twitter.com/timmo001/status/1172958335982850052?ref_src=twsrc%5Etfw">September 14, 2019</a>
<blockquote class="twitter-tweet"><p lang="en" dir="ltr">It&#39;s finally here. 🎉<br><br>Home Panel v2.0.0 is now released and has been completely rewritten in <a href="https://twitter.com/hashtag/React?src=hash&amp;ref_src=twsrc%5Etfw">#React</a> with <a href="https://twitter.com/hashtag/TypeScript?src=hash&amp;ref_src=twsrc%5Etfw">#TypeScript</a><br><br>⚠️Please read the release notes before upgrading as are backward-incompatible changes to know about before upgrading!<a href="https://t.co/NMDQu4zZW8">https://t.co/NMDQu4zZW8</a><a href="https://twitter.com/hashtag/HomePanel?src=hash&amp;ref_src=twsrc%5Etfw">#HomePanel</a> <a href="https://twitter.com/hashtag/HomeAssistant?src=hash&amp;ref_src=twsrc%5Etfw">#HomeAssistant</a> <a href="https://t.co/ucA1HxwurB">pic.twitter.com/ucA1HxwurB</a></p>&mdash; Timmo (@timmo001) <a href="https://twitter.com/timmo001/status/1172958335982850052?ref_src=twsrc%5Etfw">September 14, 2019</a>
</blockquote>
[@cogneato]: https://github.com/cogneato
@ -191,7 +191,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
<!--more-->
## 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])

2
source/_posts/2019-10-10-release-100.markdown
View File

@ -196,7 +196,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
<!--more-->
## 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])

2
source/_posts/2019-10-30-release-101.markdown
View File

@ -220,7 +220,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
<!--more-->
## 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])

2
source/_posts/2019-11-20-release-102.markdown
View File

@ -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])

4
source/_posts/2019-12-11-release-103.markdown
View File

@ -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])

6
source/_posts/2020-01-15-release-104.markdown
View File

@ -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!
<!--more-->
## 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:

6
source/_posts/2020-02-05-release-105.markdown
View File

@ -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.
</p>
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
<!--more-->
## 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])

2
source/_posts/2020-02-26-release-106.markdown
View File

@ -145,7 +145,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
<!--more-->
## 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])

2
source/_posts/2020-03-18-release-107.markdown
View File

@ -162,7 +162,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
<!--more-->
## 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])

2
source/_posts/2020-04-08-release-108.markdown
View File

@ -201,7 +201,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
<!--more-->
## 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.

6
source/_posts/2020-04-14-the-future-of-yaml.markdown
View File

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

2
source/_posts/2020-04-29-release-109.markdown
View File

@ -189,7 +189,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
<!--more-->
## 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

8
source/_posts/2020-05-20-release-110.markdown
View File

@ -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
<!--more-->
## 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:
<details>
<summary>Click see all breaking changes for ISY994</summary>
<summary>Click see all backward-incompatible changes for ISY994</summary>
- 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,

Some files were not shown because too many files have changed in this diff Show More