Home Assistant Core 2021.5.0 → 2021.6.0

HTTP (using reverse proxies)

Home Assistant will now warn when a misconfigured reverse proxy, or misconfigured Home Assistant instance when using a reverse proxy, has been detected.

These warnings will become an error in Home Assistant 2021.7.

If you are using a reverse proxy, and see these warnings, please make sure you have configured use_x_forwarded_for and trusted_proxies in your HTTP integration configuration.

For more information, see the HTTP integration documentation.

(@frenck - #51332)

Custom cards

We upgraded our frontend to use Lit 2.0. During the beta we have noticed some custom cards or views are using LitElement and lit-html from our components.

This is not a recommended practice, and might now cause the custom card to break this release. If you encounter issues with a custom card, please report this issue with the custom card developer.

Additional information about this change and information for custom card developers on how to upgrade their card, can be found in our developer blog:

"Upgrade to Lit 2.0"

Custom integrations (custom_components)

As mentioned in every release since 2021.3, custom integrations will require a version key in their manifest file.

As of this release, if that version key is missing in the manifest, the custom integration will no longer be loaded.

For more details see our developer blog about it

(@ludeeus - #49916)

1-Wire

Support for OWFS has been dropped (obsolete since 0.117).

This part of the implementation did not conform to policy regarding 3rd-party libraries of Home Assistant.

(@epenet - #50121) (onewire docs)

Denon AVR

Alexa EqualizerController has been disabled for Denon AVR since it caused Alexa to be unable to discover any devices.

(@starkillerOG - #49628) (Alexa docs)

AVM FRITZ!Box Tools

Since in most cases, the amount of really wanted to be tracked devices is quite lower than the overall count of devices, device_tracker entities will be disabled by default. You need to specifically enable wanted device_tracker, even newly detected devices.

(@mib1185 - #50791) (fritz docs)

Blebox

Blebox light no longer supports the deprecated white_value, use rgbw_color instead.

(@emontnemery - #49562) (blebox docs)

Buienradar

Buienradar is now configurable via the UI and has deprecated support for the YAML configuration. Your existing YAML configuration will be imported once.

When you have a weather and sensor setup for same coordinates, they will be merged into one integration instance. Only one camera configuration will be imported.

Following things are changed:

• The forecast key of the weather platform is deprecated, forecast data is fetched in the same API call and to be in line with ADR-0003, all available data is exposed.
• Weather, sensor and camera domain are setup in one integration. For new entries, sensor and camera entities are disabled by default.
• Dimension for camera images is fixed to 700 pixels.

(@RobBie1221 - #37796) (buienradar docs)

EE Bright Box

The integration library requirement has requirements that are conflicting with requirements of other integrations. The library maintainer hasn't responded to our issues for 10 months.

The integration is therefore disabled until the library has been fixed and Home Assistant updated with a new library version.

(@MartinHjelmare - #51069) (ee_brightbox docs)

Epson

Epson integration doesn't allow port set anymore. It uses port 80 and 3629 for communication.

(@pszafer - #45434) (epson docs)

Goal Zero Yeti

The 12V, AC, and USB binary sensors are now switches. You should update any automations and scripts that depend on these moved entities.

Before: binary_sensor.yeti_ac_port_status After: switch.yeti_ac_port_status

(@tkdrob - #48612) (goalzero docs)

HomeKit Controller

HomeKit Controller climate devices will change the reported temperature precision for their current_temperature attribute from whole degrees to 0.1 degree increments when the system is in Fahrenheit mode.

Automations which assume whole-number reporting precision may need adjustments.

(@jjlawren - #50415) (homekit_controller docs)

KNX

The create_temperature_sensors option for climate devices is now deprecated. Please use a template sensor instead.

This option created sensor entities out of climate configuration. This will not work anymore when sensor entities are also only generated from configuration.

(@farmio - #49638) (KNX docs)

---

The create_sensors option for weather entities is now deprecated. Please use template sensors instead.

This option created sensor entities out of weather configuration. This will not work anymore when sensor entities are also only generated from configuration.

(@farmio - #49640) (KNX docs)

Luftdaten

The unit of measurement for the Luftdaten pressure sensors has been adjusted from pascal (Pa) to hectopascal (hPa). The value is still the same, the unit displayed in Home Assistant was wrong and now corrected.

If you have automation or record data from this integration (externally), you might need to adjust to this change.

Modbus

The old configuration style for switches is no longer supported

# old configuration.yaml:
modbus:
    - name: "mymodbus"
      ....

switches:
    - name: "switch12"
       hub: "mymodbus"

# new configuration.yaml:
modbus:
    - name: "mymodbus"
       ....
       switches:
         - name: "switch1"

The new configuration style have changed, to secure against illegal configurations:

# before configuration.yaml:
modbus:
    - name: "mymodbus"
      ....
      switches:
          - name: "switch1"
             input_type: "holding"
             verify_state: false

# new configuration.yaml without verify:
modbus:
    - name "mymodbus"
       ....
       switches:
          - name switch1
             write_type: "holding"

# new configuration.yaml with verify:
modbus:
    - name: "mymodbus"
       ....
      switches:
        - name: "switch1"
           write_type: "holding"
           verify:

(@janiversen - #49386) (modbus docs)

---

scan_interval, if used, in any Modbus platform cannot be lower than 5 seconds. Adjustment is done automatically with a warning if needed.

Modbus timeout, if used, is automatically adjusted (with a warning) to not be higher than lowest scan interval - 1 second.

(@janiversen - #50363) (modbus docs)

MQTT

Peviously deprecated features of MQTT cover have been removed:

• Using value_template to use for extracting position is no longer allowed an error will be raised if this configuration is used, Instead of using value_template, position_template should be used.
• tilt_invert_state is removed, instead tilt_min and tilt_max should be used, error will be raised if this is found in configuration.

(@thecode - #50263) (MQTT docs)

---

If you use MQTT with the CloudMQTT broker service and have not configured a certificate for MQTT, you now need to adjust to the following:

mqtt:
  certificate: auto
  host: ... # all other info

(@balloob - #51112) (MQTT docs)

Network / Zeroconf

Network adapter configuration has moved to the UI. Users that previously used a custom zeroconf interface configuration may need to adjust the settings in the UI.

(@bdraco - #50874) (network docs)

Sonos

The device associated with Sonos speakers will report a different firmware version, switching to the more common formatted version number from now on.

(@jjlawren - #50861) (Sonos docs)

TensorFlow

Support for the TensorFlow integration is now deprecated on the Home Assistant OS, Supervised & Container installation types.

Support for it will be removed in Home Assistant 2021.7.

The use of the TensorFlow integration on the Home Assistant Core installation type, will remain available.

Tibber

Attributes for the Tibber Pulse sensor are removed and replaced by separate sensors.

Additionally the unique ID are changed, which might have caused changes to the entity IDs.

You need to to check you entities and automations and adjust them to these changes.

(@Danielhiversen - #50418) (tibber docs)

TP-Link Kasa Smart

This changes the behavior of turning a bulb when no parameters are defined. Turning on a bulb without additional parameters will now result in a "Last On" state rather than any sort of preset that may have been set in Kasa.

(@gabrialdestruir - #50334) (tplink docs)

Utility Meter

The last_reset state attribute of utility_meter sensors are now in UTC and stored as a string.

Automations and scripts accessing the last_reset state attribute may need to be updated.

(@emontnemery - #51067 #50851) (utility_meter docs)

Z-Wave JS

Z-Wave JS lights no longer support the deprecated white_value, use rgbw_color instead.

(@emontnemery - #49588) (zwave_js docs)

---

Users should update zwave-js-server to 1.7.0 or higher. If the official Home Assistant Z-Wave JS add-on is used, add-on version 0.1.23 and higher will include zwave-js-server 1.7.0.

(@MartinHjelmare - #51341) (zwave_js docs)

Farewell to the following

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

• LIFX Legacy has been removed, use the LIFX integration instead. (@frenck - #50069)
• N26 has been removed due to 3rd party API limitations. (@zhulik - #50292)
• Spot Crime access to their API cannot be gained anymore. (@frenck - #50361)