Question on Unusual Grouping - "Unavailable" group?

Configuration
1

I have numerous Yolink Sensors and once in a while (once every couple of days) one or more of them become a state of “Unavailable”. I have determined the very quickest way to bring them all back is actually to briefly cut the power to the yolink hub - the hub reboots very fast and from booting up to all the sensors being reconnected to it - is only about 15 seconds!

So I have it plugged into a smart plug and what I would like to do is have ALL of those sensors in a group - and the group would show a status of “Unavailable” if ANY of the sensors in the group are unavailable. Once I have this figured out I was going to create an automation that just toggles the power to the yolink hub once the group state becomes unavailable (but will do that no more than once every 10 minutes or so).

The above is all easy for me to do except for the underlined part above. Can this group be created in the UI - ? I can create a custom group that has logic in it to return “unavailable” if needed, but would rather not go into a bunch more coding with hard coded sensor names etc. for just determining if one of them is “unavailable”. Perfect for a group - but how do I set up the group? (Most of them would be binary_sensors I believe) - ?

(I could just have one automation with a gazillion triggers (a trigger for each of the sensors - for when it changes to a state of “Unavailable” - but that isn’t a very clean way to do it either - )?

2

Ok I guess it’ll be an automation with a massive number of triggers! Ugh

3

You can do this with a single Template binary sensor.

template:
  - binary_sensor:
      - name: "Yolink Unavailable"
        state: "{{ integration_entities('yolink') | select('is_state', 'unavailable') | list | count > 0 }}"
1 Like