0.104: Sentry, Signal Messenger, IntesisHome, Sure Petcare, KEF

The first launch of the new decade! Happy New Year!

We are starting this new year with a full launch! So let's dive!

Improved management of entities at startup

Now we are restoring all entities, stored in the registry,
at the start of Home Assistant.

During the start of Home Assistant, all of your configured integrations are
loaded. Each of these integrations results in one or more devices
and entities. However, there was a trap!

The loading of some integrations could take some time, which caused some entities
not being available immediately Sometimes, this affected multiple things, such as
missing devices in HomeKit / Google / Alexa or those big red boxes in our Lovelace
UI We are sure that, at some point, we have all experienced it.

As of this release, all these entities, if they are registered in our entity registry,
It will be restored as "not available". That allows other parts of our system to use
them immediately, solving many common problems during startup.

These restored entities can be distinguished from normal "unavailable" entities
for an additional status attribute added to those entities: "restored."

Screenshot of a removing an unavailable entity

As a result, entities will no longer "disappear," so they will be restored and not available.
The entities are removable, as shown in the screenshot above. Note that,
if an integration provides an unavailable entity, the provider integration
It must first be removed, otherwise, these entities cannot be deleted.

Ignore discovered devices and services

Do you have that device that is discovered again and again?

It is now possible to ignore a specific discovered device with a single click!

Screenshot of a discovered Hue bridge
It requires the integration to be updated to support this. For this release,
the Hue, Axis, deCONZ, WLED and HomeKit integrations are updated to support
This new feature.

Recharge all input elements and generated groups

All input_* INTEGRATIONS now they have reload
service to reload your YAML configuration for these integrations, without
the need to restart Home Assistant.

In addition, it is time to say goodbye to all groups of entities generated.
(group.all_ *). Most likely, you've never heard of them because they were
hidden. However, if you trust those groups for their automations, you
You need to adjust those automations.
Check the breaking changes section for more information.

Add a device to Lovelace

We add a button to the device page to add all the entities of a device to Lovelace
In a blink of an eye! Home Assistant suggests cards based on the type of entities that
The device provides so you can add them to a view of your choice instantly.

If you are using Lovelace in YAML mode, you can still use this new feature. the
The generated YAML can be copied and pasted into its configuration file.

Screenshot of a card suggestion for a light device
Screenshot of a card suggestion for a light device.

This same functionality is also added to the Lovelace unused entities page.

Management of selected multi entities

Entity management has never been so easy; Now lets change multiple
entities at once. Select multiple entities and delete, activate or deactivate them
with a click

Screenshot of the entities configuration page with multi selection
Screenshot of the entities configuration page with multi selection.

ZHA configuration panel improvements

@dmulcahey He did a lot of work on the ZHA configuration panel this version.

The navigation for the ZHA configuration panel has been redesigned to provide
A better user experience on mobile and desktop devices.

As part of the redesign, the complete management of the Zigbee group has been added, allowing
Create and manage Zigbee groups directly from the user interface.

Screenshot of the ZHA configuration panel
Screenshot of the ZHA configuration panel.

In future versions, the ability to link devices directly to groups,
It will be added too.

Remove your Lovelace settings

Do you want to start your Lovelace setup from scratch? Or go back to the
Lovelace interface generated automatically?

You can now erase Lovelace settings in the raw format
editor and save it.

Screenshot of the remove Lovelace confirmation dialog
Screenshot of the remove Lovelace confirmation dialog.

In other news

Meanwhile, HassOS 3.8 got released!

Besides the release of HassOS 3.8, the first beta version of HassOS 4.0 is
now available as well. This beta release adds support for
Hardkernel's ODROID-N2!

is a great and powerful alternative for the Raspberry Pi.

Custom now playing poster Lovelace card

Brad Crc made this impressive demo
of setting up a custom now playing poster card in Lovelace floor plans.
This allows you to show currently playing media in your floor plan!

Bas showing his Lovelace theme on his setup

Bas Nijholt kept seeing his own theme popping up on Reddit, so he decided it was
time for him to show off his Lovelace dashboard, featuring this lovely theme.

I keep seeing my own theme on Reddit, so now it's my turn! [OC] from r / homeassistant

His theme is publicly available on GitHub.

New integrations

New Platforms

If you need help ...

… Don't hesitate to use our very active Forums or join us for a little chat.

Experiencing issues introduced by this release? Please report them in our issue tracker.
Make sure to fill in all fields of the issue template, that is helping us a lot!

Breaking Changes

  • Default groups - Entity integrations will no longer automatically maintain the hidden groups with all of their entities. The following groups are no longer automatically created and maintained:
    • group.all_automations
    • group.all_covers
    • group.all_devices
    • group.all_fans
    • group.all_lights
    • group.all_locks
    • group.all_plants
    • group.all_remotes
    • group.all_scripts
    • group.all_switches
    • group.all_vacuum_cleaners
    • group.calendar
    • group.remember_the_milk_accounts

    The automation and script configuration panels are updated to show and manage all automations / scripts. If you want to show cards in your Lovelace UI with all entities for a single domain, use the auto-entities card. If you want to target all entities in a service call, use ALL as value for entity_id.

    (@balloob#23789) (automation docs) (calendar docs) (cover docs) (device_tracker docs) (fan docs) (light docs) (lock docs) (plant docs) (remember_the_milk docs) (remote docs) (docs script) (switch docs) (vacuum docs).

  • UPnP - UPnP / IGD units of measurement have been aligned with other integrations and common uses, they're now kB and kB / s instead of kbyte and kbyte / sec respectively. - (@scop#29552) (upnp docs)
  • Worx Landroid - The worxlandroid sensor has been changed to not return the hardcoded state values manual-stop, charging, charging-complete, going home, mowing, instead use the states given from the Landroid to Home Assistant. idle, which means that something is broken with the mower. You need to update any automations that depend on the state of the sensor. (You can use this as a notification to check the physical state of the mower.@geraldhansen#27453) (worxlandroid docs)
  • Apple iCloud - The iCloud component is no longer part of the device tracker platform and is now an integration, which is configurable via the UI. The iCloud cookie folder moved from [HA_dir] / icloud to [HA_dir] /. Storage / icloud.- (@Quentame#28968) (icloud docs)
  • Pi-hole - The default value for host is removed, and now must be specified manually. - (@johnluetke#27569) (pi_hole docs) Example configuration:
    pi_hole: - host: pi.hole ssl: false - host: backup.pi.hole
  • HERE Travel Time - HERE has deprecated the usage of app_code and new users can only generate an api_key. If you are already using HERE Travel Time, you have to follow the migration guide to retrieve the, now required, api_key. - (@eifinger#29966) (here_travel_time docs) Example configuration:
    sensor: - platform: here_travel_time api_key: "YOUR_API_KEY" origin_latitude: "51.222975" origin_longitude: "9.267577" destination_latitude: "51.257430" destination_longitude: "9.335892"
  • ZHA - The default divisor for active_power You have changed. Now, multiplier and divisor both default to 1 if the device does not support these attributes or when getting those attributes from the device fails. - (@Adminiuga#30130) (zha docs)
  • Keba - The unique_ids of the entities have changed and are now more future proof. The default name and entity_id of the entities have also changed. You need to clear stale entries from the entity registry and update concerned automations and scripts. - (@dannerph#30125) (keba docs)
  • Tesla - Config flow has been added for Tesla. Device tracker entity names have changed due to this. They now follow the naming convention of the rest of the Tesla entities. The id device tracker entity attribute was also removed because it is a duplicate of trackr_id. - (@alandtse#28744) (tesla docs)
  • Huawei LTE - The Huawei LTE notify service name is now configurable. The default name for the Huawei LTE notify service has changed to notify.huawei_lte to avoid conflicts with other notify services. An option to provide a name for the service has also been added. - (@scop#30208) (huawei_lte docs) Example configuration:
    huawei_lte: - url: ... password: ... notify: name: sms
  • Amcrest (Removed) - Amcrest sensors and switches that were deprecated in previous releases have now been removed. - (@pnbruckner#30308) (amcrest docs) Example configuration:
    amcrest: - ... sensors: # This sensor type is no longer supported and must be removed. - motion_detector # All switch types are no longer supported and must be removed. switches: - motion_detection - motion_recording
  • MQTT - Added separate command and state topics for the MQTT lock. Two new properties are introduced with state_locked (default: LOCKED) and state_unlocked (default: UNLOCKED). If you are using the same topic as state_topic as for the command_topic you can reestablish the old behavior by setting state_locked to LOCK and state_unlocked to UNLOCK. Effectively, this change allows you to distinguish commands and states in two topics with different values. - (@tuxbox#29808) (mqtt docs) Example configuration:
    lock: - platform: mqtt command_topic: "/ dev / ha / lock / cmd" state_topic: "/ dev / ha / lock / state" value_template: "" state_locked: "locked" state_unlocked: "unlocked"
  • LG webOS Smart TV - The component setup now uses the webostv domain instead of media_player. The host configuration option is now required and the timeout and filename options have been removed. The state handling for webOStv has also been cleaned up. An entity will have on when the tv is on instead of playing or Paused as was previously the case. You need to update automations that depend on the entity state. - (@bendavid#29296 #30416) (webostv docs) Example configuration:
    webostv: name: LG TV host: #other settings turn_on_action: service: wake_on_lan.send_magic_packet data: mac: "00: 00: 00: 00: 00: 00" standby_connection: true
  • Axis - Axis integration will no longer accept manual configuration of devices, all configuration of the Axis integration will now be handled from the integrations panel. - (@ Kane610#30365) (axis docs) TL; DR This will no longer work:
  • WLED - Improved WLED pure white support for RGBW LED strips. When using WLED with RGBW strips, setting the color in Home Assistant to white, will turn off the RGB LEDs of the strip and use the W channel only. - (@frenck#30477) (wled docs)
  • timer - Fire restarted event on restarting an active timer. This can break automations that should trigger on every timer start event. - (@mnigbur#30475) (timer docs)
  • Vice - Removed suppress_warning from configuration options for Vizio integration. The pyvizio package now suppresses insecure HTTPS request warnings in a way that doesn't affect global requests from other integrations or Home Assistant itself. There is no need to globally suppress insecure warnings now. - (@ raman325#30536) (vizio docs) Example configuration:
    media_player: - platform: vizio host: '<IP>: <PORT>' access_token: '<AUTH_TOKEN>' device_class: tv
  • RFXtrx - Bump pyRFXtrx to 0.25. This update switches the commands for open and close for RFXtrx covers of the “Rollertrol” type, as they were switched (clicking open resulted in closing of the cover and vice versa). Existing automations should be updated. - (@ Ernst79#30566) (rfxtrx docs)
  • Ring - Ring is now configurable via a config entry. This means it will no longer store the username and password and you're able to configure accounts that use 2FA. It's no longer possible to set scan interval, monitored conditions or FFmpeg arguments. The defaults are used. - (@balloob#30564) (ring docs)
  • Binary Sensor (Locks) - Updated ON / OFF condition and triggers to match the documentation and UI. This change inverts the logic of automations relating to binary sensor with the lock device class, but only for automations triggering on the lock state (rather than triggering a lock / unlock action). If you already created automations, you will need to check those, as they probably need to be inverted. The text displayed in the trigger or condition dropdowns in Lovelace will now be correct.One possible scenario is if you have set an automation using the state of one lock to trigger an action on other lock (s). This change would cause the action to trigger on locking if it was previously triggering on unlocking. - (@ davet2001#30663) (binary_sensor docs)

Beta Fixes

All changes

A %d bloggers like this: