Home Assistant Core 2022.10.0 → 2022.11.0

Unit: Revolutions per minute (rpm)

Multiple integrations provide sensors with the revolutions per minute unit. Two units have been used throughout Home Assistant to indicate this: RPM and rpm.

This release standardizes all integrations to use the lowercase rpm variant. The following integrations have been adjusted:

• Big Ass Fans
• Danfoss Air
• Glances
• System Bridge
• Universal Devices ISY994
• Vallox

Home Assistant automatically handles this change of units. However, if you record history externally (for example, using InfluxDB), you might need to adjust to this change.

(@epenet - #79986 #79987 #79988 #79989 #79990 #79992)

Android IP Webcam

The previously deprecated YAML configuration of the Android IP Webcam integration has been removed.

Android IP Webcam 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.

(@engrbm87 - #80875) (documentation)

Anthem A/V Receivers

The previously deprecated YAML configuration of the Anthem A/V Receivers integration has been removed.

Anthem A/V Receivers are 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.

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

APC UPS Daemon

The UPS Last Self Test sensor is renamed to UPS Self Test Result and a new UPS Last Self Test sensor reports time instead of the result.

You may need to replace sensor.ups_last_self_test with sensor.ups_self_test_result in automations and scripts referencing the sensor.ups_last_self_test entity.

(@definitio - #80773) (documentation)

Brother Printer

The counter and remaining pages attributes of the sensors drum remaining life, black drum remaining life, cyan drum remaining life, magenta drum remaining life, and yellow drum remaining life have been migrated to their own dedicated sensor entities.

If you are using these attributes in your automation or script, you will need to adopt those for this change.

(@bieniu - #79932) (documentation)

ClickSend TTS

• The caller option from ClickSend TTS notify service has been removed, as it prevented calls from being actually made.
• The default name has been changed to clicksend_tts instead of an empty name; otherwise the service would appear as notify.notify. Now it will, by default, appear as notify.clicksend_tts. This might impact your automation or script.
• The recipient's phone number now must match E.164 format.

(@CharlieBailly - #76669) (documentation)

Coinbase

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

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

(@epenet - #80084) (documentation)

Dark Sky

When Darksky is configured to report in US units, the unit of measurement for precipitation intensity has been corrected from inches to inches per hour.

(@epenet - #80611) (documentation)

ecobee

Setting up the notify platform of the ecobee integration by a platform section using YAML configuration is no longer supported. The ecobee platform section under notify: can be safely removed from your YAML configuration files.

The thermostat index can be specified by using the target parameter in the notify service call instead.

(@kevdliu - #78558) (documentation)

HERE Travel Time

The route sensor has been removed, as it could contain more data than the Home Assistant state engine is able to hold. Make sure you update any automations or scripts that use this sensor.

(@eifinger - #79211) (documentation)

HomeKit

HomeKit instance ID assignments are now stable between restarts to comply with the HomeKit specifications. This prevents accessories from losing track of services between restarts, and improves stability with using Siri especially with apple watches.

This change may dramatically improve the stability and re-sync times of media_player entities (all), camera entities (all), fan entities (presets), remote entities (activity ones), switch entities (power strips) triggers (all) between restarts which was especially apparent when the home has many accessories.

Because the assignments were previously unstable, it may be necessary to make a one-time adjustment of accessory room assignments, favorites, or re-pair camera accessories after upgrading.

(@bdraco - #79913) (documentation)

HomeKit Controller

As older versions did not correctly set service identifier values, it may be necessary to unpair and re-pair some BLE devices or to delete duplicate entities manually.

If the service identifiers were loaded incorrectly when the device was paired with an older version, operations might raise StopIteration or RuntimeError errors. You can correct those by deleting the integration for that device, and doing a one-time re-pairing.

(@bdraco - #80798) (documentation)

Hunter Douglas PowerView

This change ceases creating battery sensors for hardwired shades. Existing sensor entities need to be manually deleted.

(@kingy444 - #81013) (documentation)

IntelliFire

The backing unit and the API of the device itself uses 0-4 as a flame height setting. Through discussion on the forums the community has decided 1-5 is a much more logical setting for flame height, and accordingly, this has been implemented.

If you set the flame height using automations or scripts, you will need to adapt those to this change.

(@jeeftor - #79901) (documentation)

Logger

logger no longer changes the default log level of Home Assistant to debug if used without a value for default. It will now only change the default log level of Home Assistant from a warning to something else if the default is explicitly specified.

If you do not specify default and want Home Assistant to have a default log level of debug, you will need to add this to your YAML configuration:

logger:
  default: debug

(@mdegat01 - #80033) (documentation)

Open Exchange Rates

The previously deprecated YAML configuration of the Open Exchange Rates integration has been removed.

Open Exchange Rates 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.

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

Scrape

Previously, scrape would return the last correct value if an HTTP request for updating failed. This has been adjusted to now mark the sensor as unavailable instead.

(@epenet - #80593) (documentation)

Templates (fan)

Template fans no longer change their state to on when set_percentage or set_preset_mode is called when a value_template has been configured.

(@Petro31 - #75656) (documentation)