Home Assistant Core 2022.4.0 → 2022.5.0

Configuration Menu

This release contains several changes to the configuration menu. These are the most important changes.

• The Configuration menu has been renamed to Settings.
• Helpers moved to Devices & services.
• Blueprints moved to Automations & Scenes.
• Areas is now grouped with `Zones.
• Dashboard Resources moved to overflow menu*.
• A brand new System menu housing all system-related settings:

• The Restart button is available in the System menu.
• New Updates menu, which also now provides the ability to join or leave the beta channel from the overflow menu*.
• All logs moved to Logs (Supervisor, audio, etc).
• Backups moved from the Supervisor/Main menu to here.
• Network now has all network related settings previously in the General settings and Supervisor.
• Storage provides information about used space, eMMC Lifetime, and also provides the Move datadisk feature in the overflow menu*.
• Hardware now has the Reboot and Restart Host controls, Available Hardware is available in the overflow menu*.
• System Health moved to its own menu item in the system menu.
• Processor and memory usage was moved into the new System Health menu.
• The integration list with timings, previously shown in the About menu, is moved into the new System Health menu.

Additionally, the developers tools has a brand new YAML tab, which contains the buttons and tools to reload and check your YAML configuration. This was previously known as "Server Controls", but now moved to the developer tools.

* The overflow menu is the menu you see when you click on the three vertical dots in the top right of your screen.

Temperature conversion

Sensors reporting a temperature but not setting device class to temperature will no longer have their values automatically converted. For sensors that are manually configured, users need to set the device class. If the integration providing the sensor does not support setting device class, the sensor's state can be filtered through a template sensor.

(@emontnemery - #69069)

AVM FRITZ!Box Call Monitor

The previously deprecated YAML configuration of the AVM FRITZ!Box Call Monitor integration has been removed.

AVM FRITZ!Box Call Monitor 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.

(@cdce8p - #70829) (documentation)

AVM FRITZ!Box Tools

The binary sensor entity showing that an update is available for the FRITZ!Box firmware has been deprecated and will be removed in Home Assistant 2022.7.

The AVM FRITZ!Box Tools integration now provides an update entity as a replacement.

(@Mask3007 - #70096) (documentation)

BMW Connected Drive

All bmw_connected_drive.* services are removed (deprecated since 2022.2). Please use the new button entities with the button.press service instead.

(@rikroe - #69808) (documentation)

---

The button.<your_vehicle_refresh entity is deprecated and will be removed in a future version. Please use the homeassistant.update_entity service with any BMW entity to force-refresh all platforms from the BMW API.

(@rikroe - #67003) (documentation)

deCONZ

Migrating deCONZ Siren entities from switch platform to siren platform has been removed. This only affects users upgrading from before 2021.10 to 2022.5 or later. At most, this causes lingering unavailable switch entities; which can be manually removed.

(@Kane610 - #70600) (documentation)

---

Migrated deCONZ light entities of type "On/Off Output" to switch from light platform as they are binary devices (only on/off).

(@Kane610 - #70598) (documentation)

Energy

The internal cost and compensation sensor entities, used by the energy dashboard of Home Assistant, are now hidden by default.

(@frenck - #70378) (documentation)

Fibaro

Fibaro lights no longer support deprecated white_value, use rgbw_color instead.

(@rappenze - #69189) (documentation)

Flick Electric

Units changed from cents to ¢/kWh. This more accurately represents the type of value, and makes the sensor work when used in the Energy dashboards.

If you relied on this unit of measurement format in your automations, scripts, or have been recording it in an external time metrics database, you may need to adapt to this change.

(@ZephireNZ - #69396) (documentation)

History Stats

The pretty formatted value attribute has been removed in favor of using the new duration state class, which is formatted by the frontend.

This change significantly reduces the number of rows stored in the database.

(@bdraco - #70720) (documentation)

HomeKit

The device class carbon_dioxide is no longer admitted as a binary_sensor device class; as it is not a valid device class for a binary sensor. If you have overridden the device class with customize you need to adjust your configuration.

(@epenet - #69239) (documentation)

IKEA TRÅDFRI

The native IKEA TRÅDFRI groups are now removed. We propose using light groups instead.

Additionally, the previously deprecated YAML configuration of the IKEA TRÅDFRI integration has been removed.

IKEA TRÅDFRI 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.

(@ggravlingen - #68033) (documentation)

Integration - Riemann sum integral

The Integration sensor unit configuration parameter was deprecated in Home Assistant Core release 2021.10 and is now removed as it did not take unit_prefix and unit_time into account.

Example:

sensor:
  - platform: integration
    source: sensor.current_power
    name: energy_spent
    unit_prefix: k
    unit_time: h
    unit: MWs
    round: 2

The configuration in the example would cause the source sensor's unit (e.g., W) to be overruled and the integration sensor's unit_of_measurement would be set to MWs (MegaWatt-Second) even though the integral calculation was performed with k (kilo) and h (hour), i.e., the value of the integration sensor is in kWh, not MWs.

(@dgomes - #69157) (documentation)

LIFX

The LIFX integration changed the network adapters used to discover LIFX devices. Instead of enabling all adapters on which LIFX devices appear, it now only uses the adapter(s) enabled in Home Assistant.

This makes the discovery of LIFX faster and more reliable.

(@Djelibeybi - #70458) (documentation)

Media Player

Media Player now supports a new state, buffering. Integrations supporting this state previously reported playing but may now report buffering. This may also introduce new state transitions between the two states during playback.

In order to maintain previous behavior, replace usage of playing with both the buffering and playing states, and consider how to handle transitions between the two.

(@emontnemery - #70863) (documentation)

Media Source

Filenames and directories starting with a . will no longer appear in the Media Browser.

If the file or directory name starts with a ., it means they are marked hidden; thus, the media browser will now respect that.

(@DDanii - #69820) (documentation)

Min/Max

min_max sensors generated a significant amount of database rows because they included all attributes regardless of the configured type. For active sensors, these attributes added up to multiple megabytes per day for each sensor. Reference issue report.

min_max sensors now only set attributes based on the configured type of sensor as below:

• min: min_entity_id
• max: max_entity_id
• last: last_entity_id

The following attributes are no longer present: min, max, mean, median, last, count_sensors

If access to the data previously provided by the attributes is needed, create a separate min_max sensor for that required type instead.

(@bdraco - #70142) (documentation)

MJPEG IP Camera

The previously deprecated YAML configuration of the MJPEG IP Camera integration has been removed.

MJPEG IP Camera 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 - #68033) (documentation)

ONVIF

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

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

(@hunterjm - #70395) (documentation)

Pentair ScreenLogic

The original orp_supply_level and ph_supply_level sensors will become unavailable. Two new sensors will be automatically created, but the originals will have to be removed and the new ones manually renamed to match the originals.

This should only affect those with IntelliChem.

(@dieselrabbit - #69937) (documentation)

Phone Modem

The previously deprecated modem_callerid.reject_call service has now been removed. A button entity has previously been made available as a replacement.

(@frenck - #69019) (documentation)

Radarr

The previously deprecated "Wanted" sensor in the Radarr integration has been removed. If you have this sensor still configured in your YAML configuration, you should remove it before updating.

(@tkdrob - #69500) (documentation)

RainMachine

RainMachine zone switches no longer have the time_remaining attribute; instead, each zone now has a separate sensor entity (device class of timestamp, entity category of diagnostic) that shows the datetime at which the zone will finish (or last finished if the zone isn't running).

(@bachya - #69206) (documentation)

---

RainMachine switch attributes that are floats are now rounded to two decimals of precision.

(@bachya - #70006) (documentation)

Recorder

Home Assistant will now automatically repack your database once a month, on the second Sunday of the month.

Repacking allows shrinking the database in file size, resulting in smaller backups. It also frees up the space that has been freed up by the database optimizations made in 2022.4.

Some notes:

• It is only done once a month to minimize I/O.
• The second Sunday was chosen as it would be out of sync with Home Assistant releases.
• This automatic repacking can be disabled by setting auto_repack to false in the recorder configuration.

(@bdraco - #69314) (documentation)

---

It's no longer possible to configure the recorder to use an in-memory database.

(@emontnemery - #69616) (documentation)

---

Integrations and platforms can provide hints to the recorder to exclude specific entity state attributes from being recorded.

This excludes attributes that hold little to no historical value or are a static value. This significantly reduces the amount of data stored.

The following attributes are no longer recorded:

• Automation: current, id, last_action, last_triggered, max and mode.
• Input Boolean: editable.
• Input Button: editable.
• Input Datetime: editable, has_date, and has_datetime.
• Input Number: editable, max, min, mode, and step.
• Input Text: editable, max, min, mode, and pattern.
• Input Select: editable.

(@bdraco - #70168 #70223)

(@frenck - #70154 #70224 #70225 #70226)

SABnzbd

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

(@shaiu - #68138) (documentation)

Sensibo

The binary sensor for the update available has been removed. Use the new update entities to monitor available updates instead.

(@gjohansson-ST - #70180) (documentation)

Sonos

The sonos_group attribute on Sonos media players has been renamed to group_members to align with other integrations.

(@jjlawren - #70924) (documentation)

SQL

The SQL integration migrated to configuration via the UI. Configuring SQL 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 - #68700) (documentation)

Steam

The Steam integration migrated to configuration via the UI. Configuring Steam 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 first account listed in the YAML configuration will be considered as your Steam ID as there is no way to identify your Steam ID from your API key. You can put your Steam ID as the first entry in accounts before updating, or set up the integration from scratch.

(@tkdrob - #67261) (documentation)

Synology DSM

The naming of entities and devices has been aligned, so that the device name is now part of the entity name.

(@mib1185 - #69754) (documentation)

Tautulli

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

(@tkdrob - #57450) (documentation)

Templates

Trigger-based template sensors are now initialized to the last known state at Home Assistant startup, instead of to "unknown".

(@emontnemery - #69344) (documentation)

text-to-speech (TTS)

The TTS base_url option is deprecated. Please, configure internal/external URL instead.

(@balloob - #70382) (documentation)

UPnP/IGD

The UPnP/IGD integration options have been removed. This includes the ability to configure a custom update/scan interval.

As an alternative, the more generic and more flexible homeassistant.update_entity service can be used to create an automation that updates the entities on your desired intervals or schedule.

(@StevenLooman - #69134) (documentation)

Vera

Vera power meter sensor is now using the (correct) symbol W for watt instead of watts.

If you relied on this unit of measurement format in your automations, scripts, or have been recording it in an external time metrics database, you may need to adapt to this change.

(@emontnemery - #69285) (documentation)

Z-Wave JS

With this release, you will need to update your zwave-js-server instance.

• If you use the zwave_js add-on, you need to have at least version 0.1.56.
• If you use the Z-Wave JS 2 MQTT add-on, you need to have at least version 0.38.0.
• If you use the zwavejs2mqtt Docker container, you need to have at least version 6.7.0.
• If you run your own Docker container, or some other installation method, you will need to update your zwave-js-server instance to at least 1.16.0.

(@raman325 - #70464) (documentation)

Zengge

Zengge lights no longer support white_value, please use white instead.

(@emontnemery - #55260) (documentation)

Farewell to the following

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

• Arlo has been removed. It was in a broken state for a long time caused by authentication changes upstream. (@anaisbetts - #70330)
• Digital Loggers has been removed. It relied on web scraping, which is not allowed for a Home Assistant Core integration. (@tkdrob - #69939)
• Updater was previously deprecated and has been removed. Use the Version and Analytics integrations as a replacement. (@frenck - #68981)