0.116: Entities card row editor, restore snapshots and performance metrics

This release contains breaking changes for custom card developers, check the
developers blog
for more information.

If you have a custom card that stopped working this release, please report
this with the custom card author.

YAML support for AlarmDecoder has been removed in favor of UI configuration.
Additionally, the panel_display option has been removed and the alarm display
sensor will always be created with AlarmDecoder now. Please see the updated
AlarmDecoder documentation for instructions on how to
set up AlarmDecoder via the UI.

(@ajschmidt8 – #37998) (alarmdecoder docs)

State conditions with attribute specified: When testing against a non-string
attribute value, you now need to specify the value in your configuration in the
same type as it is in the attribute (instead of as a string).

(@balloob – #41261)

Canary is now available for configuration via the UI. This also means its no
longer configured in YAML. Existing configurations should be automatically
transitioned to configuration via UI. You can safely remove you Canary YAML
configuration after ugprading. YAML support will be fully removed in
Home Assistant 0.118.0.

(@ctalkington – #40055) (canary docs)

Some integrations (homekit_controller, plant, smartthings
and xiaomi_miio) previously used lux as their unit of measurement for
entities that covered illuminance. Now, these entities use lx as their unit
of measurement to be consistent with other integrations.

This could be a breaking change for using such entities in,
for example, influxdb.

(@springstan – #40171)

Fixes the Hyperion Integration to work with the current Hyperion-NG release.
Refactors to rely on the
hyperion-py client.

The default_color, hdmi_priority and effect_list parameters no longer have
any effect. Instead, users should use light profiles
as default color.

The effect_list is now automatically populated.

The hdmi_priority parameter no longer make sense with Hyperion-NG and will
be removed in a future release.

(@dermotduffy – #39738) (hyperion docs)

We changed the way how we handle binary sensors in the underlying library. It
is no longer possible to support automations based on the binary_sensor
schema. Instead, you can use the new counter state attribute for any given
KNX binary sensor.

Before this change:

-  name: cover_abstell
   state_address: "2/0/33"
   automation:
     - counter: 1
       hook: 'on'
       action:
         - entity_id: cover.sonne_abstellkammer
           service: cover.open_cover
     - counter: 1
       hook: 'off'
       action:
         - entity_id: cover.sonne_abstellkammer
           service: cover.close_cover

After this change:

# binary_sensor.yaml
- name: cover_abstell
  state_address: "2/0/33"

# automation.yaml
automation:
  - alias: 'Binary sensor test counter=1 on'
    trigger:
      platform: numeric_state
      entity_id: binary_sensor.cover_abstell
      attribute: counter
      above: 0
      below: 2
    condition:
      - condition: state
        entity_id: binary_sensor.cover_abstell
        state: 'on'
    action:
      - service: cover.open_cover
        entity_id: cover.sonne_abstellkammer

  - alias: 'Binary sensor test counter=1 off'
    trigger:
      platform: numeric_state
      entity_id: binary_sensor.cover_abstell
      attribute: counter
      above: 0
      below: 2
    condition:
      - condition: state
        entity_id: binary_sensor.cover_abstell
        state: 'off'
    action:
      - service: cover.close_cover
        entity_id: cover.sonne_abstellkammer

If you intend to use the counter feature (counter > 1) make sure you also
enable ignore_internal_state (default: true) for your binary_sensor and
set the new context_timeout attribute to the time in between you want it to
react to your sensor clicks (defaults to 1 – which should be fine).
Otherwise, the counter will not work correctly.

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

Message and domain are now removed from the logbook state_changed events.

These are now handled by the frontend as we move closer to making the logbook
localized.

(@bdraco – #40070) (logbook docs)

The Material Design Icons are updated to v5.6.55, the mdi:scooter icon is
replaced by a new icon, the old icon is available as mdi:human-scooter

Lights using the Pilight integration will now turn on to the last used
brightness instead of its maximum brightness.

If you want to retain you lights turning on to its maximum brightness you can
set the default intensity in the light_profiles.csv file.

The steps to set this up:

1. In the your main config folder (where you’ll find configuration.yaml)
   create a new file called light_profiles.csv.
2. For each of lights add an line with its entity id and the brightness
   you want, as a value from 0 to 255.

Example:

light.<deviceentityid>.default,0,0,255

(@daniel-jong – #39549) (pilight docs)

The Synology integration is now deprecated. You should now use the Synology DSM
instead. Support for cameras has been added to the Synology DSM integration
making it a full replacement.

(@shenxn – #39958) (synology docs)

Not really a breaking change, since the overall logic did not change. Arguments
that were previously mandatory for sensors of this integration are still
mandatory and optional arguments remain optional.

However, we now enforce those mandatory arguments to be present,
since otherwise this integration creates entities that cannot do anything,
e.g., the sensor for IPv4 addresses cannot do anything if no network interface
is specified from which to take the IP.

If the integration fails to load, check the log to see which arguments are
missing in your configuration. The documentation also has been updated to
clearly show which arguments are mandatory.

(@spacegaier – #39687) (systemmonitor docs)

The TekSavvy integration has been removed. The API that was used by this
integration is no longer available.

(@mikeodr – #40762)

The Kelvin unit no longer includes the degree sign in accordance with
scientific standards. If you use the isy994 and lcn integrations you may
need to update automations or data collectors that depend on the unit of
measurement.

(@RichieFrame – #40574) (isy994 docs)

The auto fan mode for the fan platform has been removed. The auto mode isn’t
supported by the entity model in Home Assistant and was initially added
overlooking our entity model.

If you have automations or scripts targeting the VeSync fan entity should
review these and update as needed.

(@TheGardenMonkey – #40559) (vesync docs)

The ieee_address parameter was renamed to ieee for zha.permit
and zha.remove services.

This makes all services to use consistently named parameters.

(@Adminiuga – #40652) (zha docs)