Maybe I am missing something(?), but there really should be a dedicated list of offline devices in both the web and mobile apps.
Sometimes, for whatever reason, devices go offline and I am not aware of it until the Flows using those devices do not trigger or fail. By that point, the issue has already caused problems. It would make a big difference to be able to clearly see which devices are offline.
It would be very useful to have a category in the web app Devices tab, at the top above “Home”, called “Offline” or another suitable name, that lists all offline devices. The same should apply to the mobile app, placed at the top where Lights, Activity, Energy, Climate, and the other categories are listed.
This is basic UX functionality. Devices are at the core of Homey, so having a clear overview of offline devices should be standard.
Nah, you can have/should have yourself informed prior to that situation (an offline devices list), with this flow card of the Device Capabilities app, so you can fix it before it turns into a “list” of offline devices (I think this “list” should not have the chance to appear/grow):
I agree it should be prevented before it happens but…
Using the Device Capabilities app to sniff for offline devices would mean creating a flow for every single device. That is manageable when adding new devices one by one, but it is far less practical when there are already 200 devices set up. It would also likely put extra stress on Homey if it is constantly running checks in the background(?)
Then there is the issue of how I am informed about offline devices. It works fine if Homey sends one or two notifications when a couple of devices go offline. It becomes a problem when multiple devices fail at the same time. I end up flooded with notifications. At that point I know something is wrong, but when I open the Homey web app I still do not have a clear list of which devices are offline and have to go through each room individually to find them.
So it is a great idea to use Device Capabilities and thank you for the suggestion. In the absence of a better solution, I will gradually start adding flows to monitor my “usual suspects”. However, that does not excuse Athom from providing a simple way to quickly see which devices are offline. I really hope they do something about it.
