Home Assistant Core 2021.10.0 → 2021.11.0

All Service Calls

Entities that are now shown on the device page on the configuration or diagnostic section, will no longer be targeted and called by service calls that target the specific device or area the device or entity is in.

If you need to make a service call to these entities, you will need to call them by their entity ID explicitly.

Please note: This does not apply to entity groups, as groups are explicitly based on entities (unlike areas) and thus still work as before.

(@emontnemery - #57671)

Amazon Alexa / Google Assistant

Entities that are now shown on the device page on the configuration or diagnostic section, will no longer be exposed by default to Amazon Alexa or Google Assistant.

If you want to expose these entities, you'll need to expose them explicitly.

(@emontnemery)

Recorder / Databases

The Home Assistant project has now explicitly defined a set of databases that are supported by the recorder.

We now support the following databases:

• MariaDB ≥ 10.3
• MySQL ≥ 8.0
• PostgreSQL ≥ 12
• SQLite ≥ 3.32.1

All other databases and database versions are now deprecated.

If your used or configured database doesn't match any of the above requirements, a warning will be logged. As of Home Assistant 2022.1, the recorder will no longer connect to an unsupported database.

(@emontnemery - #58161) (recorder docs)

---

It is no longer possible to filter out state_changed events from the recorder's event_types exclude filter.

A warning will be logged in Home Assistant Core 2021.11 and the configuration will be rejected in Home Assistant Core 2022.2.

Python 3.8: Deprecation warning

Python 3.8 has been deprecated because Python 3.10 has been released. Support will be dropped in Home Assistant 2022.1.

Support for Python 3.10 hasn't completed yet, however we aim to complete that before the 3.8 deprecation period has ended. It is advised to upgrade to Python 3.9 at this point.

If you run Home Assistant OS, Supervised or the Container installation type: No action is required from your end, we will take care of this for you.

(@balloob - #57079)

Aurora ABB Solar PV

The Aurora ABB Solar PV integration migrated to configuration via the UI. Configuring Aurora ABB Solar PV via YAML configuration has been deprecated and will be removed in a future Home Assistant release.

Your existing YAML configuration is automatically imported on upgrade to this release; and thus can be safely removed from your YAML configuration after upgrading.

(@davet2001 - #36300) (aurora_abb_powerone docs)

AVM FRITZ!Box Tools

AVM FRITZ!Box Tools services now ask for a device_id and no longer for an entity_id. Please review your automation and scripts accordingly.

(@chemelli74 - #58005) (fritz docs)

DLNA Digital Media Renderer

The DLNA Digital Media Renderer integration migrated to configuration via the UI. Configuring DLNA Digital Media Renderer via YAML configuration has been deprecated and will be removed in a future Home Assistant release.

Your existing YAML configuration is automatically imported on upgrade to this release; Please check the integrations configuration page for imported DLNA-DMR configuration. Once it has been migrated, it can be safely removed from your YAML configuration.

(@chishm - #56886) (dlna_dmr docs)

Efergy

The Efergy integration has been migrated to configuration via the UI. Configuring Efergy via YAML configuration has now been deprecated and will be removed in a future Home Assistant release.

Your existing YAML configuration is automatically imported on upgrade to this release; and thus can be safely removed from your YAML configuration after upgrading.

Additionally, the following sensor names have changed:

• Energy Usage is now Power Usage.
• Any configured energy period, for example, monthly was Energy Consumed is now Monthly Consumption.
• Any configured cost period, for example, monthly was Energy Cost is now Monthly Energy Cost.
• Per-Device Usage is now Power Usage with the sensor id trailing.

(@tkdrob - #56890) (efergy docs)

Environment Canada

The Environment Canada integration has been migrated to configuration via the UI. Configuring Environment Canada via YAML configuration has now been deprecated and will be removed in a future Home Assistant release.

Your existing YAML configuration is automatically imported on upgrade to this release; and thus can be safely removed from your YAML configuration after upgrading.

Additionally, non-loop radar images are no longer supported; Sensor entities now have the location of the station as a part of the sensor's entity name.

(@gwww - #57127) (environment_canada docs)

Flux LED/MagicLight

The Flux LED integration has been migrated to configuration via the UI. Configuring Flux LED via YAML configuration has now been deprecated and will be removed in a future Home Assistant release.

Your existing YAML configuration is automatically imported on upgrade to this release; and thus can be safely removed from your YAML configuration after upgrading.

(@icemanch - #56354) (flux_led docs)

HomeKit

The previously deprecated HomeKit configuration options safe_mode, zeroconf_default_interface, and auto_start have now been removed.

If you still have these options in your YAML configuration, you must be remove them from your YAML configuration.

(@bdraco - #58320)

Input Select / Dropdown Helper

When the option list of a Dropdown helper / input_select is updated, it will try to maintain the currently selected option, if the selected option also is present in the new options provided; otherwise it will reset to the first option from the newly provided list.

Previously, when a new list of options was provided, it would always reset to the first item of the list.

(@frenck - #53334) (input_select docs)

IQVIA

Previously, IQVIA supported long-term statistics for the Asthma Index: Tomorrow sensor. This is incorrect: long-term statistics are meant for actual, current measurements (not future forecasts). Therefore, long-term statistics support has been removed for this sensor.

(@bachya - #57687) (iqvia docs)

Itho Daalderop Spider

The Itho Daalderop Spider integration previously migrated to configuration via the UI. Configuring Itho Daalderop Spider via YAML configuration has now been deprecated and will be removed in a future Home Assistant release.

Your existing YAML configuration has been automatically imported; and thus can be safely removed from your YAML configuration after upgrading.

(@peternijssen - #57974) (spider docs)

Microsoft text-to-speech (TTS)

The default voice is changed to JennyNeural; The previous default ZiraRUS (Standard Voice) is no longer supported in eastus or any other region that has rolled out GA neural voices as Standard voices become deprecated.

(@tylergibson - #58499) (microsoft docs)

OctoPrint

The OctoPrint integration migrated to configuration via the UI. Configuring OctoPrint via YAML configuration has been deprecated and will be removed in a future Home Assistant release.

Your existing YAML configuration is automatically imported on upgrade to this release; and thus can be safely removed from your YAML configuration after upgrading.

The following sensors have been removed:

• sensor.<printer>_time_remaining
• sensor.<printer>_time_elapsed

The following sensors have been added:

• sensor.octoprint_start_time
• sensor.octoprint_estimated_finish_time

(@rfleming71 - #58040) (octoprint docs)

OpenGarage

The attributes (wifi_signal and distance_sensor) for OpenGarage covers are removed and replaced by individual sensors.

Also, door_state is removed as an attribute, but you can use the state directly instead.

Please update any automations or scripts that depend on the removed attributes.

(@Danielhiversen - #57976) (opengarage docs)

OpenZWave

The OpenZWave (ozw) integration is being marked as deprecated. The upstream project is not currently being maintained, and has not reached stable status.

We recommend transitioning to the Z-Wave JS integration.

While the integration is not currently slated for removal, it will no longer be receiving updates and may be removed at a later date.

See the Z-Wave JS migration documentation for more information.

Pentair ScreenLogic

Screenlogic lights have moved to the light platform. The switches that previously represented these lights will need to manually be deleted in Configuration >> Entities. If you are using these switch entities in your automation or scripts, you will need to update those to use the new light entities instead.

The state is now refreshed with a short delay to ensure the toggles do not flip/flop between states as the controller takes ~600ms to make the change.

(@bdraco - #55467) (screenlogic docs)

Phone Modem

The sensor state attributes of modem_callerid integration are now only populated when the values are known.

If you use these attributes in your automations or scripts, you'll need to adjust those to be able to handle missing attributes.

(@tkdrob - #57774) (modem_callerid docs)

Rainforest Eagle

The previously deprecated YAML configuration of the Rainforest Eagle integration has been removed.

Rainforest Eagle is now configured via the UI, any existing YAML configuration has been imported in previous releases and can now be safely removed from your YAML configuration files.

(@frenck - #57636) (rainforest_eagle docs)

RainMachine

RainMachine services have been reorganized and now utilize a Home Assistant target (entity ID) or selector (device ID) instead of using an internal RainMachine identifier.

Additionally, services are restricted to only the targets that apply:

Device Services (i.e., must be provided a device ID)

• pause_watering
• stop_all
• unpause_watering

Entity Services (i.e., must be provided an associated switch entity ID [either a program or a zone])

• disable_program
• disable_zone
• enable_program
• enable_zone
• start_program
• start_zone
• stop_program
• stop_zone

(@bachya - #57145) (rainmachine docs)

Renault

The last_update state attribute has been moved to a stand-alone entity (and dropped from battery and location entities). If you used this attribute in your scripts or automations; you'll need to adjust those to this change.

(@epenet - #57750) (renault docs)

SimpliSafe

SimpliSafe requires a new web-based authentication method. When starting up, Home Assistant will automatically prompt you to re-authorize your instance.

(@bachya - #57212) (simplisafe docs)

SolarEdge

The SolarEdge integration now provides unique IDs for its entities, so the entities are now visible and customizable in the Home Assistant frontend.

Some names have been corrected as they had incorrect descriptions. This may cause some of your entity IDs provided by SolarEdge to have changed this release.

In case you have been using these entities in your automations, scripts, or dashboards, you can either rename those entity IDs to the old entity ID or adjust the places you've used them accordingly.

Additionally, if a sensor you used disappeared, it might have been disabled by default during upgrade. Please be sure to check if the entity is enabled in that case.

(@terminet85 - #55902) - (@purcell-lab - #58773)

Sonos

The sonos.set_option service has been removed and replaced with individual switch entities which both control the features and display if currently enabled.

The night_sound and speech_enhance attributes on the Sonos media_player entities are also removed.

If you are using those in your automations or scripts, you'll need to replace these with the new switch entities.

(@jjlawren - #54502) (sonos docs)

Stookalert

The Stookalert integration has been migrated to configuration via the UI. Configuring Stookalert via YAML configuration has now been deprecated and will be removed in a future Home Assistant release.

Your existing YAML configuration is automatically imported on upgrade to this release; and thus can be safely removed from your YAML configuration after upgrading.

(@frenck - #57119) (stookalert docs)

Supervisor

The 2021.09 release deprecated the usage of "snapshot" in the Supervisor (hassio) integration and was scheduled to be removed in 2021.11, that is now.

Old services and service data that contained "snapshot" has now been removed, and you need to update your configuration if you use any of these to continue to use it.

If you used the snapshot argument for the restore services you now have to replace that with slug

Example:

# Old name
service: hassio.restore_full
data:
  snapshot: sn2321

# New name
service: hassio.restore_full
data:
  slug: sn2321

(@ludeeus - #57652) (hassio docs)

UptimeRobot

The previously deprecated YAML configuration of the UptimeRobot integration has been removed.

UptimeRobot is now configured via the UI, any existing YAML configuration has been imported in previous releases and can now be safely removed from your YAML configuration files.

(@ludeeus - #57761) (uptimerobot docs)

Utility Meter

The offset parameter for utility_meter sensors is now limited to at most 27 days. If you used more then 27 days you must now migrate to cron.

(@dgomes - #55625) (utility_meter docs)

Venstar

The Venstar integration migrated to configuration via the UI. Configuring Venstar via YAML configuration has been deprecated and will be removed in a future Home Assistant release.

Your existing YAML configuration is automatically imported on upgrade to this release; and thus can be safely removed from your YAML configuration after upgrading.

The humidifer and timeout options have been removed, and thus ignored when importing your YAML configuration into the UI.

(@garbled1 - #58152) (venstar docs)

Viessmann ViCare

Due to upstream library updates, a breaking change was introduced that required changes to sensor and binary_sensor entities.

Circuit, Burner and Compressor have been separated out from the "main" device. Multiple circuits and burners now allow "duplicate sensors", we've added the circuit or burner number as suffix.

Most of you should not see a difference, but complex installations (with more than one circuit and/or burner), will have multiple entities, suffixed with their burner or entity IDs.

For example, if you have two circuits instead of a single climate.vicare entity you will now instead have two entities:

• climate.vicare_1
• climate.vicare_2

This will provide you more control, but requires you to adapt your existing scripts and automations to use the new entity IDs.

The same has been done for sensor, binary_sensor and water_heater entities.

Also, note that binary sensors might be created twice since the unique IDs for those entities have changed. Please remove the old disabled binary_sensor entities, in case you encounter this.

(@oischinger - #57700) (vicare docs)

VLC media player Telnet

The VLC media player Telnet integration migrated to configuration via the UI. Configuring VLC media player Telnet via YAML configuration has been deprecated and will be removed in a future Home Assistant release.

Your existing YAML configuration is automatically imported on upgrade to this release; and thus can be safely removed from your YAML configuration after upgrading.

(@MartinHjelmare - #57513) (vlc_telnet docs)

Xiaomi Miio

Attributes from the vacuum entities have been replaced with sensors.

This means that all your references to these attributes must be replaced with its sensor in your automations, scripts and dashboards.

Some sensors have been disabled by default and need manual enablement, once the integration has been set up. For example, the attribute mop_attached: true has now been replaced with binary_sensor.<NAME>_mop_attached.

(@OGKevin - #54990) (xiaomi_miio docs)

Yeelight

The option to override the Yeelight model will only appear if the detected model is not in the database. Otherwise, it will be hidden.

(@bdraco - #56967) (yeelight docs)

Farewell to the following

The following integrations are no longer available as of this release:

• Essent has been removed. The API is no longer usable for this integration and has therefore been removed. (@TheLastProject - #56991)
• Lyft has been previously deprecated and now removed. API keys are no longer being provided. (@frenck - #57638)
• Nello has been removed. The services are no longer available, and have been offline for over 6 months. (@pattyland - #57926)
• Huawei Router has been removed. It relies on web scraping, which is no longer allowed. (@yuvalabou - #57136)
• Wink has been previously deprecated and now removed. (@frenck - #57634)