Helpers - Groups - Updates

I would like to see update.* device group make its way into the helper ui

Currently, I use a conditional card to display who has available updates. I will manually make a template sensor to watch all update entities so I can put a badge on my main dashboard if an update is available.
It would be a nice addition to have it managed via UI in my opinion and should be pretty simple to add considering they are binary sensors just under a different group.

Much love,
Chris

+1 for this. Love the new update entities and assumed that as the state is actually a binary sensor, you could group these sensors. However the device class is firmware or none, so adding these as a group via yaml throws an error. I believe it is simply allowing these 2 additional device classes to be grouped.

db

Here’s what I did for now (Requires Mushroom Cards for UI) – Hopefully it will help you in your current use case. I still would love to see this become part of ‘Helpers’ though.

Inside of Groups.yaml (Can’t remember if I made this and import it in the configuration.yaml)

update_devices:
  name: update_available
  entities:
    - update.amcrest2mqtt_update
    - update.attic_sw
    - update.backyard_ap
    - update.frontyard_ap
    - update.home_assistant_core_update
    - update.home_assistant_operating_system_update
    - update.home_assistant_supervisor_update
    - update.limited_guest_access_update
    - update.livingrm_sw
    - update.mariadb_update
    - update.mosquitto_broker_update
    - update.multipurposerm_ap
    - update.nginx_proxy_manager_update
    - update.node_red_update
    - update.office_sw
    - update.pi_hole_core_update_available
    - update.pi_hole_ftl_update_available
    - update.pi_hole_web_update_available
    - update.rack_aggregation
    - update.rack_ap
    - update.rack_sw
    - update.samba_backup_update
    - update.samba_share_update
    - update.ssh_web_terminal_update
    - update.studio_code_server_update
    - update.udmpro

UI - Mushroom Card

type: custom:mushroom-template-card
primary: |-
  {% if (user == "Chris") %}
  Nerd Stuff
  {% else %}
  {% endif %}
secondary: >-
  {% if (user == "Chris") %}

  {% if (states.group.update_devices.state == "on") or
  (states.sensor.hacs.state|float > 0) %}

  Update Available

  {% else %}

  No Updates ATM

  {% endif %}

  {% else %}

  {% endif %}
icon: |-
  {% if (user == "Chris") %}
  mdi:home
  {% else %}
  {% endif %}
badge_icon: >-
  {% if (user == "Chris") %}

  {% if (states.group.update_devices.state == "on") or
  (states.sensor.hacs.state|float > 0) %}

  mdi:arrow-up-bold-hexagon-outline

  {% else %}

  {% endif %}

  {% else %}

  {% endif %}
badge_color: >-
  {% if (user == "Chris") %}

  {% if (states.group.update_devices.state == "on") or
  (states.sensor.hacs.state|float > 0) %}

  red

  {% else %}

  {% endif %}

  {% else %}

  {% endif %}
tap_action:
  action: navigate
  navigation_path: nerdstuff
hold_action:
  action: navigate
  navigation_path: nerdstuff
double_tap_action:
  action: none
icon_color: >-
  {% if (user == "Chris") %}

  {% if (states.group.update_devices.state == "on") or
  (states.sensor.hacs.state|float > 0) %}

  red

  {% else %}

  green

  {% endif %}

  {% else %}

  {% endif %}

Also, in another page on my UI – I have a list of available updates

type: custom:auto-entities
card:
  type: entities
  title: Updates Available
  state_color: true
  show_header_toggle: false
filter:
  include:
    - domain: update
    - entity_id: sensor.hacs
  exclude:
    - state: '*off*'
    - state: '*unavailable*'
sort:
  method: last_changed
show_empty: false