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

¡El primer lanzamiento de la nueva década! ¡Feliz año nuevo!

¡Estamos comenzando este nuevo año con un lanzamiento completo! ¡Así que vamos a sumergirnos!

Manejo mejorado de entidades al inicio

Ahora estamos restaurando todas las entidades, almacenadas en el registro,
en el inicio de Home Assistant.

Durante el inicio de Home Assistant, todas sus integraciones configuradas son
cargado. Cada una de esas integraciones da como resultado uno o más dispositivos
y entidades. Sin embargo, hubo una trampa!

La carga de algunas integraciones podría llevar un tiempo, lo que provocó que algunas entidades
no estar disponible de inmediato A veces, esto afectó múltiples cosas, como
dispositivos faltantes en HomeKit / Google / Alexa o esos grandes cuadros rojos en nuestro Lovelace
UI Estamos seguros de que, en algún momento, todos lo hemos experimentado.

A partir de este lanzamiento, todas estas entidades, si están registradas en nuestro registro de entidades,
será restaurado como «no disponible». Eso permite que otras partes de nuestro sistema utilicen
ellos inmediatamente, resolviendo muchos problemas comunes durante el inicio.

Estas entidades restauradas se pueden diferenciar de las entidades normales «no disponibles»
por un atributo de estado adicional agregado a esas entidades: «restaurado».

Screenshot of a removing an unavailable entity

Como resultado, las entidades ya no «desaparecerán», por lo que se restaurarán y no estarán disponibles.
Las entidades son extraíbles, como se muestra en la captura de pantalla anterior. Tenga en cuenta que,
si una integración proporciona una entidad no disponible, la integración proveedora
primero debe eliminarse, de lo contrario, esas entidades no pueden eliminarse.

Ignorar dispositivos y servicios descubiertos

¿Tienes ese dispositivo que se descubre una y otra vez?

¡Ahora es posible ignorar un dispositivo descubierto específico con un solo clic!

Screenshot of a discovered Hue bridge
Requiere que la integración se actualice para admitir esto. Para este lanzamiento,
las integraciones Hue, Axis, deCONZ, WLED y HomeKit se actualizan para admitir
Esta nueva característica.

Recargue todos los elementos de entrada y grupos generados

Todas las input_* integrations ahora tienen reload
servicio para recargar su configuración YAML para estas integraciones, sin
la necesidad de reiniciar Home Assistant.

Además, es hora de decir adiós a todos los grupos de entidades generados.
(group.all_*). Lo más probable es que nunca hayas oído hablar de ellos porque eran
oculto. Sin embargo, si confía en esos grupos para sus automatizaciones, usted
necesita ajustar esas automatizaciones.
Revisar la breaking changes section para más información.

Agregar un dispositivo a Lovelace

Agregamos un botón a la página del dispositivo para agregar todas las entidades de un dispositivo a Lovelace
en un abrir y cerrar de ojos! Home Assistant sugiere tarjetas basadas en el tipo de entidades que
el dispositivo proporciona para que pueda agregarlos a una vista de su elección al instante.

Si está usando Lovelace en modo YAML, aún puede usar esta nueva función. los
El YAML generado se puede copiar y pegar en su archivo de configuración.

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

Esta misma funcionalidad también se agrega a la página de entidades no utilizadas de Lovelace.

Gestión de entidades multi seleccionadas

La gestión de entidades nunca ha sido tan fácil; Ahora permite cambiar múltiples
entidades a la vez. Seleccione varias entidades y elimínelas, actívelas o desactívelas
con un clic

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

Mejoras en el panel de configuración de ZHA

@dmulcahey hizo mucho trabajo en el panel de configuración de ZHA esta versión.

La navegación para el panel de configuración ZHA se ha rediseñado para proporcionar
Una mejor experiencia de usuario en dispositivos móviles y de escritorio.

Como parte del rediseño, se ha agregado la gestión completa del grupo Zigbee, lo que permite
crear y gestionar grupos Zigbee directamente desde la interfaz de usuario.

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

En futuras versiones, la capacidad de vincular dispositivos directamente a grupos,
será agregado también.

Eliminar su configuración de Lovelace

¿Desea comenzar su configuración de Lovelace desde cero? O volver a la
interfaz Lovelace generada automáticamente?

Ahora puede borrar la configuración de Lovelace en la configuración sin formato
editor y guardarlo.

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!

The 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) (script docs) (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.This includes the state idle, which means that something is broken with the mower. You can use this as a notification to check the physical state of the mower.You need to update any automations that depend on the state of the sensor.(@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 has 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: 192.168.1.53
        #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:
    axis:
    
  • 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)
  • Vizio – 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 blogueros les gusta esto: