Home Assistant Core 2020.12.0 → 2021.1.0

Météo-France

The unit of measurement of the UV sensor was missing and has been added. You may have to adapt your configuration accordingly, if you were depending on the unit of this sensor in any automations, scripts or 3rd party data loggers.

(@mbo18 - #43992) (meteo_france docs)

Glances

Previously, the Glances integration was presuming that all sensors were temperatures. Now, we can distinguish temperatures, fan speeds and battery charges.

In consequence, those entities have new Entity IDs, so you should update your configuration in the UI or in your YAML files.

Previously, they were all suffixed by _temp. Now they are suffixed by _temperature, _fan_speed and _charge.

Examples:

• sensor.glances_core_0_temp => sensor.glances_core_0_temperature
• sensor.glances_battery_temp => sensor.glances_battery_charge
• sensor.glances_thinkpad_1_temp => sensor.glances_thinkpad_1_fan_speed

(@guix77 - #43500) (glances docs)

Neato

Neato now uses a new authentication method: OAuth2.

If you are an existing Neato user, you will need to update your YAML configuration, as per the updated Neato documentation. The integration will then automatically be migrated.

Vorwerk support is dropped from the neato integration. The parent library still supports Vorwerk however, the authentication is completely different and therefore will require a separate integration created.

(@Santobert - #44031) (neato docs)

Tado

The Tado Bridge sensor has been removed and replaced by its corresponding device sensor.

(@Noltari - #44475) (tado docs)

OpenTherm Gateway

This release breaks binary_sensor and sensor entities of the opentherm_gw integration. More specifically, all existing binary_sensor and sensor entities are recreated with a different entity_id, unique_id and friendly name.

Some entities are recreated once, others will be recreated twice for different data sources (boiler and thermostat). All entities that are recreated are disabled by default.

The old sensor and binary_sensor entities will log a deprecation warning and change behavior slightly if they are enabled. They will be automatically removed if they are disabled. Behavioral changes of the old entities may include a delayed update and a possible change of data source (boiler vs. thermostat) which may only become apparent when an override is active on the OpenTherm Gateway.

The climate entity is not affected.

The OpenTherm Gateway sits between the thermostat and the boiler and thus deals with 2 streams of information. Before this release, the status info we received contained overlapping information from both streams of information, which led to issues when the gateway was overriding some values.

As of this release, the status is split up in multiple parts to reflect this. Each part contains the status of its respective information stream. With this change, we create sensor entities for each stream where necessary.

(@mvn23 - #43352) (opentherm_gw docs)

BMW Connected Drive

BMW Connected Drive has been migrated for configuration via the UI.

Your old entries from configuration.yaml are automatically imported __once__ for initial setup.

It is recommended to rename the device_tracker of your car(s) in config/known_devices.yaml (you can e.g., add _old to the entity name) before updating, otherwise a second device tracker entity (ending with _2) per car will be created.

After updating, the entity can be removed from known_devices as that will no longer be used.

(@rikroe - #39585) (bmw_connected_drive docs)

Farewell to the following

The following integrations have been removed:

• Avri (@timvancann - #44478)

Avri has changed their API and it seems not possible to use the new one.