Home Assistant Core 2021.11.0 → 2021.12.0

customize.yaml UI (customization)

The customize.yaml UI (customization) has been removed. The YAML configuration for this is recommended and remains available. To customize entities, use the entity settings available via the icon in the top right of the entity "more info" dialog (when clicking on an entity). Entity settings now also allows customizing device_class for certain binary_sensor and cover cases.

A small explanation why it has been removed:

With customize, one is changing the state machine directly, without any checks. This comes at a risk. Additionally, for many use cases (like: name, icon, device class) one should edit the entity via the UI instead, which is possible for the greater part of the entities nowadays.

The old customize UI is confusing in many ways and has a level of power that, if wielded incorrectly, can have unforeseen consequences. Someone found and used the customize UI first, and then things are out of sync throughout the UI, as the internal entity registry would show the old values.

The customize UI also relied on setting up an include and YAML configuration to begin with; which already made it an advanced feature.

Therefore, the customize UI was removed and remains available as an advanced YAML feature, additionally we have added the capability, to adjust the common device_class changes using the "Show as" feature while editing the entity from UI.

Add-ons, Backups & Supervisor

The Supervisor panel has been merged into the configuration panel. The separate menu item from the sidebar has been removed.

---

The binary_sensor with "running" device_class that was provided for the Home Assistant Operating System device did not work and has now been removed; If you have added this to templates or automations, remove it from your configuration.

(@ludeeus - #60597) (hassio docs)

Companion App

The Companion App configuration has been merged into the configuration panel. The separate menu item from the sidebar has been removed.

Advantage Air

The HVAC mode for zone climate entities was set to FAN or OFF, because the actual HVAC mode is set for the entire ducted AC system. However, using FAN means the Google Home app won't let you set a target temperature, so it has been changed to AUTO instead.

(@Bre77 - #52816) (advantage_air docs)

BMW ConnectedDrive

The following services/sensors have been removed due to not being available using the My BMW API:

• alltrips_*
• lasttrips_*
• chargingconnectiontype
• charginginductivepositioning
• lastchargingendreason
• lastchargingendresult
• maxelectricrange

Attributes of binary_sensor.doors and binary_sensor.windows do not start with door/window anymore.

notify requires a location attribute at data.location, as the MyBMW API only supports sending POI and not messages.

The find_vehicle service will always send the location of your Home Assistant instance to BMW.

(@rikroe - #59881 #60938) (bmw_connected_drive docs)

Brunt Blind Engine

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

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

Additionally, the Brunt integration can now be reloaded via the Integrations screen in the frontend and will also reload if a Brunt device is removed from your account.

(@eavanvalkenburg - #49714) (brunt docs)

Fronius

The Fronius integration migrated to configuration via the UI. Configuring Fronius 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.

This change will remove manual configuration of Fronius device IDs. Connected SolarNet devices will be detected automatically on startup.

(@farmio - #59686) (fronius docs)

Guardian

Guardian services have been reorganized and now utilize a Home Assistant selector (device ID) instead of using a Guardian entity.

(@bachya - #58632) (guardian docs)

HomeKit Controller

This release removes the air quality from HomeKit Controller as the platform has been previously deprecated.

The air quality values have been broken out as their own sensors starting from September, making them easier to incorporate in your dashboard widgets, graphs, and automations. These should be used instead.

(@Jc2k - #60480) (homekit_controller docs)

Hue

Events for Hue remotes/switches

Philips/Signify streamlined the events that are emitted for remotes/switches; these are now no longer device specific but more generic. This means that if you're relying on the hue_event to trigger events emitted by these devices, the event_data will now be slightly different. To easily identify what events get emitted by your Hue remotes, Open Developer Tools and subscribe to the hue_event.

Light entities for Hue rooms/zones

Entities for Hue groups (zones/rooms) will be imported but in a disabled state by default. The Integration option to enable Hue groups has been phased out in favor of the default Home Assistant functionality to enable/disable entities.

To enable any (new) light entities for Hue groups: Open settings --> integrations --> Hue --> Entities --> Click one of the disabled entities and enable it.

Existing Hue group lights for rooms/zones will be migrated as enabled entities.

Legacy Hue groups of type LightGroup (which are not visible in the official Hue app) will no longer be supported!

Entities for Hue scenes

If you create any scenes for your Hue zones/rooms, these will now be automatically imported to Home Assistant as scene entity, including support for the new Hue Dynamic Scenes. You can disable any scene entities you don't like to use in Home Assistant (or delete them in the Hue app).

(@marcelveldt - #58996) (hue docs)

KNX

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

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

Additionally, the KNX integration can now be reloaded via the Integrations screen in the frontend, and thus the knx.reload service has been removed.

(@marvin-w - #59377) (knx docs)

---

The last_knx_update attribute has been removed from the KNX sensors and binary sensors. The last_update attribute can be used alternatively.

If you are relying on this attribute in your automations or script, you will need to adjust them to this change.

(@farmio - #58786) (knx docs)

---

The configuration key event_filter is now deprecated and will be removed in a future version of Home Assistant. Please use the new event config key instead.

(@farmio - #57621) (knx docs)

Kostal Plenticore

The "Battery Strategy" sensor has been removed from the Kostal Plenticore integration. It is replaced by a switch and a select entity to allow setting the battery charging settings from Home Assistant.

(@slowflyer - #56529) (kostal_plenticore docs)

Litter-Robot

The litterrobot.reset_waste_drawer and litterrobot.set_wait_time services are deprecated and replaced by dedicated button entities; please use those instead.

(@natekspencer - #59734) (litterrobot docs)

Material Design Icons (MDI)

The previously deprecated MDI icons, now have been removed.

The following icons have been removed:

• adobe-acrobat
• adobe
• amazon-alexa
• amazon
• android-auto
• android-debug-bridge
• bandcamp
• battlenet
• blogger
• buffer
• cash-usd-outline
• cash-usd
• cellphone-android (alternative: cellphone)
• cellphone-iphone (alternative: cellphone)
• concourse-ci
• currency-usd-circle
• currency-usd-circle-outline
• do-not-disturb-off (alternative: minus-circle-off)
• do-not-disturb (alternative: minus-circle)
• douban
• file-pdf (alternative: file-pdf-box)
• file-pdf-outline (alternative: file-pdf-box)
• file-pdf-box-outline (alternative: file-pdf-box)
• google-photos
• home-currency-usd
• laptop-chromebook (alternative: laptop)
• laptop-mac (alternative: laptop)
• laptop-windows (alternative: laptop)
• microsoft-edge-legacy
• microsoft-yammer
• pdf-box (alternative: file-pdf-box)
• plus-one (alternative: numeric-positive-1)
• poll-box (alternative: chart-box)
• poll-box-outline (alternative: chart-box-outline)
• tablet-ipad (alternative: tablet)
• telegram
• untappd
• vk
• xamarian-outline
• xing
• y-combinator

The following icons have been renamed:

• apple-airplay to cast-variant
• application to application-outline
• application-cog to application-cog-outline
• application-settings to application-settings-outline
• bolnisi-cross to cross-bolnisi
• boom-gate-up to boom-gate-arrow-up
• boom-gate-up-outline to boom-gate-arrow-up-outline
• boom-gate-down to boom-gate-arrow-down
• boom-gate-down-outline to boom-gate-arrow-down-outline
• buddhism to dharmachakra
• cellphone-erase to cellphone-remove
• celtic-cross to cross-celtic
• christianity to cross
• christianity-outline to cross-outline
• face to face-man
• face-outline to face-man-outline
• face-profile-woman to face-woman-profile
• face-shimmer to face-man-shimmer
• face-shimmer-outline to face-man-shimmer-outline
• flash-circle to lightning-bolt-circle
• floor-lamp-variant to floor-lamp-torchiere-variant
• gif to file-gif-box
• gradient to gradient-vertical
• hand to hand-front-right
• hand-left to hand-back-left
• hand-right to hand-back-right
• hinduism to om
• human-greeting to human-greeting-variant
• iframe to application-brackets
• iframe-outline to application-brackets-outline
• iframe-array to application-array
• iframe-array-outline to application-array-outline
• iframe-braces to application-braces
• iframe-braces-outline to application-braces-outline
• iframe-parentheses to application-parentheses
• iframe-parentheses-outline to application-parentheses-outline
• iframe-variable to application-variable
• iframe-variable-outline to application-variable-outline
• islam to star-crescent
• judaism to star-david
• monitor-clean to monitor-shimmer
• pharmacy to mortar-pestle-plus
• sparkles to shimmer
• teach to human-male-board
• television-clean to television-shimmer
• text-subject to text-long
• twitter-retweet to repeat-variant
• voice-off to account-voice-off

MQTT

The following previously deprecated MQTT fan options are no longer supported and have been removed:

• payload_high_speed
• payload_low_speed
• payload_medium_speed
• speed_command_topic
• speed_list
• speed_state_topic
• speed_value_template

(@jbouwh - #58992) (mqtt docs)

Notifications for Android TV

The Notifications for Android TV integration allows you to send custom notifications to Android TV devices. Sending a file along with the notification, allows you to send image files that will show up above the notification.

Now that support for icons has been added in the same way as images, the file option has been renamed to image to properly identify what you're sending with the notification.

As such, code and automations that use the file option for an image have to refer to image from now on.

(@redahb - #60159) (nfandroidtv docs)

Pentair ScreenLogic

Screenlogic SCG levels have moved to the number platform to support setting of these values. The sensor entities that previously represented these values will need to be manually deleted in Configuration -> Entities.

(@dieselrabbit - #60872) (screenlogic docs)

Phone Modem

The previously deprecated YAML configuration of the Phone Modem integration has been removed. Phone Modem 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.

(@tkdrob - #59526) (modem_callerid docs)

RainMachine

The rainmachine.disable_program, rainmachine.enable_program, rainmachine.disable_zone, and rainmachine.enable_zone services have been removed.

Instead, new configuration switches related to each entity can be used to enable/disable the program/zone.

(@bachya - #59617) (rainmachine docs)

Renault

The renault.charge_start service is deprecated and replaced by a dedicated start charge button entity; please use that entity to start the charge instead.

(@epenet - #59383) (renault docs)

SimpliSafe

SimpliSafe services have been reorganized and now utilize a Home Assistant selector (device ID) instead of using a SimpliSafe system ID.

(@bachya - #58722) (simplisafe docs)

SMA Solar

Previously when the inverter was not supplying any power, the sensors showed as Unknown. These sensors will now show the value of 0, making it more useful for graphs or calculations.

(@rklomp - #59848) (sma docs)

Sonos

The sonos.set_option service has been removed along with the bass_level and treble_level attributes on media_player entities.

Controls for bass and treble adjustments have been moved to dedicated number entities.

(@jjlawren - #60498) (sonos docs)

Statistics

All statistical characteristics were removed from sensor attributes and are now selectable through state_characteristic as the state of the sensor. The parameter state_characteristic will become mandatory in a future release.

Please adapt the configuration of your statistics sensor(s) and expose the characteristic you are interested in directly through state_characteristic. Existing template sensors to access individual characteristics can be removed. In case you are interested in multiple characteristics, you need to define multiple statistics sensors.

Many characteristics were renamed and additional ones were added, including a few for binary source sensors. Consider opening a feature request if your use case is not directly covered.

(@ThomDietrich - #59867) (statistics docs)

Templates: timestamp_local and timestamp_utc

The timestamp_local and timestamp_utc template functions/filters have changed their output format. The timestamp is now formatted to iso standards and contains timezone information.

Previously a timestamp from these would look like: 2016-07-21 16:39:04. Now it is formatted as: 2016-07-21T16:39:04+01:00.

This change may break templates that need a specific format, in those cases, you can use the timestamp_custom template filter instead.

(@jbouwh - #60269)

Trafikverket Weather Station

The Trafikverket Weather Station integration migrated to configuration via the UI. Configuring Trafikverket Weather Station 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.

(@gjohansson-ST - #60078) (trafikverket_weatherstation docs)

Twente Milieu

Due to the modernization of the Twente Milieu integration; the twentemilieu.update service has been removed.

You can now use the homeassistant.update_entity service with the Twente Milieu integration as a replacement for the removed service.

(@frenck - #59632) (twentemilieu docs)

Velbus

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

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

(@Cereal2nd - #60411) (velbus docs)

Viessmann ViCare

The Viessmann ViCare integration migrated to configuration via the UI. Configuring Viessmann ViCare 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.

(@oischinger - #56691) (vicare docs)

WLED

The led_count and max_power attributes have been removed from the sensor entity that provides the estimated current of the WLED device. These have been replaced by their own sensor entities.

If you have been using the attributes in your automation or scripts, you'll need to adjust those to reflect these changes.

(@frenck - #58839) (wled docs)

---

The speed, palette name, intensity, and reverse effect indicator attributes have been removed from the WLED light entities. They all have been replaced by their own, dedicated, number and switch entities.

If you rely on these attributes in your automations or scripts, you'll need to adjust those to this change.

(@frenck - #60535) (wled docs)

---

The wled.effect and wled.preset services have been removed. For both services, full replacements are available as normal entities in Home Assistant.

If you are still using these services in your automation or script, please replace them with service calls to their native entities instead.

(@frenck - #60537) (wled docs)

Yamaha MusicCast

Only one Home Assistant device was created for a Yamaha MusicCast device, and the media player entities of all zones were part of this device.

As of this release, every zone media player will be located in its own Home Assistant device. For single zone devices, nothing will change and all your automations, scripts, scenes, etc., should work in the same way as before.

A new device will be created for multi-zone devices for every non-main zone (e.g., zone2 or zone3). The media_player of the main-zone will remain in the original device with all its properties, scripts, automations and scenes, configured for it.

For other zones, you will have to set the area of the newly generated devices for the various zones manually. If you created scripts, automations, or scenes with the device as a target and want them to work for non-main zones, you will have to add the newly added devices as a target to your script/automation/scene.

If you used the media player entity as a target, everything should still work like before.

(@micha91 - #58285) (yamaha_musiccast docs)

Z-Wave JS

Some entities have been marked as configuration entities, e.g., default tone of siren devices and protection mode of smart plugs.

Configuration entities:

• Are not included in a service call targeting a whole device or area.
• Are, by default, not exposed to Google Assistant or Alexa.
• Are shown on a separate card on the device configuration page.
• Do not show up on the automatically generated Lovelace Dashboards.

(@MartinHjelmare - #59157 #58703 #59474) (zwave_js docs)

Farewell to the following

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

• Dyson has been removed. The integration has been broken for a long time now, so its time for it to go, (@epenet - #59401)
• IOTA has been removed. The protocol is no longer compatible/usable with this integration. (@lambtho12 - #59380
• Loop Energy has been removed. Loop has shutdown their API in November 2020. (@cgarwood- #61175)
• myChevrolet has been removed. It has been broken for 6 months and GM keeps actively hardening their authentication; preventing the integration to work. (@sdague - #59629)