Check availability of all devices

alebr001 · April 17, 2024, 9:30pm

Is there a way to target all devices for a status change trigger, without having to individually list them? The number of devices in my smart home is increasing steadily and every so often a device becomes unavailable. Rather than finding out that a motion sensor or switch is not available anymore when I use the device, I would like to get updated on my phone that I need to re(-)pair a device.

Thanks!

ddaniel · April 17, 2024, 9:33pm

There are a lot of solutions for that. Google around. Im using uptime kuma to track devices avability. If device is not availsble it will send me message on my telegram account.

MaxK · April 17, 2024, 9:42pm

github.com

jazzyisj/unavailable-entities-sensor/blob/main/README.md

## What does this template sensor do?
This sensor iterates the state object and returns entities that have a state of unknown or unavailable.

The sensor state is a count of unavailable entities and the entity_id attribute is a list of those entity id's.

## Requirements ##
To use this template as is you must be running at least Home Assistant v2022.5.

## How do I use this sensor?
### Install As Package
The easiest way to use this sensor is to install it as a [package](https://www.home-assistant.io/docs/configuration/packages/).

If you already have packages enabled in your configuration, download [`package_unavailable_entities.yaml`](https://github.com/jazzyisj/unavailable-entities-sensor/blob/main/package_unavailable_entities.yaml) to your packages directory.

To enable packages in your configuation, create a folder in your config directory named `packages` and add the following line to your `configuration.yaml` file.

    homeassistant:
      packages: !include_dir_named packages
### Install Without Packages
To create this sensor without using packages simply copy the relevant template code to an appropriate place in your configuration.yaml file. The ignored entities group and example automation are optional.

This file has been truncated. show original

Stiltjack · April 17, 2024, 9:47pm

Trouble is, devices are not marked unavailable until several hours after they have stopped responding. This is because battery-powered devices can’t be contacted by the coordinator, they have to initiate a connection.

The ZHA Toolkit from HACS has a “ping” service - presumably that gives up after x tries.

Edit: If you have Zigbee devices going unavailable often enough to need to track them, I’d suggest you look into the reason. XY problem.

MaxK · April 17, 2024, 9:59pm

For battery powered devices, I would also recommend a battery monitoring automation to detect when batteries are low (belt & suspenders).