0.118: Grid and logbook cards, quick navigation, native template types

(@frenck – #42351) (ptvsd docs)

Per ADR-0010, this PR deprecates YAML configuration for Flu Near You
until 0.119.

Existing YAML configuration has already been imported automatically in the
previous releases and can now safely be removed from your configuration files.

(@bachya – #42535) (flunearyou docs)

DirecTV has fully transitioned to configuration via UI. YAML configuration is
no longer supported. Existing YAML configuration has already been imported
automatically in the previous releases and can now safely be removed from your
configuration files.

(@ctalkington – #41961) (directv docs)

Roku has fully transitioned to configuration via UI. YAML configuration is
no longer supported. Existing YAML configuration has already been imported
automatically in the previous releases and can now safely be removed from your
configuration files.

(@ctalkington – #41960) (roku docs)

This breaking change is for custom component developers only!

The template.helpers.extract_entities has been removed as it has not been
used in core, been deprecated, and thrown warnings since the new template system
tracking was introduced.

homeassistant.helpers.event.async_track_template_result should be used instead.

(@bdraco – #42601)

OpenWeatherMap has fully transitioned to configuration via UI. YAML
configuration is no longer supported. Existing YAML configuration has already
been imported automatically in the previous releases and can now safely be
removed from your configuration files.

Additionally, previously the OpenWeatherMap integration used Pa as their unit
of measurement for air pressure. However, air pressure is measured and reported
as hPa so the unit of measurement has been changed to hPa. This could be a
breaking change for using such entities in, for example, influxdb.

(@nzapponi – #39839) (@randyxxl – #42801) (openweathermap docs)

Shelly devices configured with new (fw >= 1.9) property “appliance_type” can
now be added to the light domain instead of the switch domain.

(@chemelli74 – #42508) (shelly docs)

The Epson integration is now configured via the UI. Existing YAML configuration
if automatically imported on upgrade and can be safely removed afterward.

The SSL option has been remove, as there is no signs that anybody used it with
success.

(@pszafer – #39697) (epson docs)

The integration will not consider bounding box geometries anymore when
calculating the distance to an event from the feed. In practice it has turned
out that these bounding boxes are way too large around the event to make them
useful for the purpose of notifying users about these events.

Any existing configuration will continue to work and does not need to be
modified. However, please consider changing the radius defined for your
integration to match your expectations, especially if your main concern are
widespread and moving events such as tropical cyclones.

(@exxamalte – #42957) (gdacs docs)

This feature was introduced as an opt-in beta feature in Home Assistant Core
0.117, and is now enabled by default.

A template would always result in a string (text). This made it hard to use
things like lists, or numbers as a result of a template. For example, returning
a list of entities or an RGB/HS/XY color.

This change may impact your existing templates, as templates now can return
other types; For example, string, float, integer, boolean, lists
or dictionaries.

The following templates can be impacted by this:

• Entities with templated attributes. Attributes keep their native Python type,
  thus if the attribute is used/processed in a template again later,
  the type might be different.
• Templates working with lists or mappings (dictionaries). Previously, such
  collection would be returned as a text, for example [1, 2, 3, 4, 5]. We’ve
  seen examples where such results are decoded using text processing again
  (e.g., by splitting the result on a, to get the separate values). The
  additional processing is no longer needed, as the returned value will be a
  collection now.
• Note: The entity state in Home Assistant is always a text (string). Even with
  native types being supported in Templates now if a result is stored as an
  entity state, they will be converted to a string.

In case this new feature causes a problem for you, you can enable the old-style
template rendering again, by setting the following configuration:

homeassistant:
  legacy_templates: true

Please note, this option is a temporary/transitional option, that will be
removed in the future. Adjusting your templates to the new situation is
therefore advised.

(@frenck – #42967)

Entities for this integration now use a “timestamp” device class. Therefore,
the timetamp attributes have been removed.

(@yuvalabou – #41397) (jewish_calendar docs)

This release contains updates to improve stability and support newer Sisyphus
table firmwares. There is a small chance that older firmwares will have issues
with this release; if you have trouble with the Sisyphus integration after this
update, make sure your table is running at least firmware 1.10.73.

(@jkeljo – #42995) (sisyphus docs)

As of July 26, 2020, due to an API change; You now must provide a sensor_id
for the Neurio sensor to work; otherwise, an error returns that the request
is unauthorized.

(@czechmark – #42728) (neurio_energy docs)

Per ADR-0010, this PR deprecates YAML configuration for AirVisual until 0.119.
If you already use the AirVisual integration, you do not need to take action,
as your configuration has already been imported into the UI.

(@bachya – #42581) (airvisual docs)

Per ADR-0010, this release deprecates YAML configuration for Notion
until 0.119.

Existing YAML configuration will be imported automatically when upgrading
and can be safely removed from your configuration files afterward.

(@bachya – #43026) (notion docs)

The default value for password was set to “admin” in the
fritz and fritzbox_callmonitor integrations. This has been corrected and
moved to be the default value for the configuration option of username.

Per ADR-0010, this release deprecates YAML configuration for Tile until 0.119.

Existing YAML configuration will be imported automatically when upgrading
and can be safely removed from your configuration files afterward.

(@bachya – #43064) (tile docs)

The parameter context_timeout is now optional for binary sensors and will
default to None. If you’ve previously not specified this parameter you’ll have
to adjust your configuration and add it like this:

knx:
  binary_sensor:
    - name: sensor
      state_address: "1/2/3"
      context_timeout: 1.0

This prevents users that do not use this feature from waiting one second until
automations are triggered.

The parameter reset_after for binary sensors expects seconds now instead of
milliseconds to streamline the different configuration options.
(context_timeout also uses seconds).

The parameter ignore_internal_state for binary sensors now defaults to False
as most users do not use this feature. It defaulted to True before.

If you have validation errors of your configuration after the update and you
are using the operation_modes parameter for your climate devices, please add
all erroneous entries to the new controller_modes parameter.

(@marvin-w – #42026) (knx docs)