# Monitoring or logging errors in devices

**URL:** <https://community.homey.app/t/monitoring-or-logging-errors-in-devices/149106>\
**Category:** Questions & Help\
**Created:** [January 12, 2026, 12:26pm UTC](https://community.homey.app/t/monitoring-or-logging-errors-in-devices/149106 "2026-01-12T12:26:39Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Johan\_Taal](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/johan_taal/32/9807_2.png) [@Johan\_Taal](https://community.homey.app/u/Johan_Taal)\
**Post date:** [January 12, 2026, 12:26pm UTC](https://community.homey.app/t/monitoring-or-logging-errors-in-devices/149106/1 "2026-01-12T12:26:39Z")

</div>

I’m looking for an app or a workaround to monitoring or logging devices with a warming like in this screen ( a triangle with a exclamation mark). Is that possible?

 ![previewhtmlclipboarditem_thum](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/1/71156c8f5f078e9c4ed074da2d4792dac8917f34.jpeg)

---

<div class="post-metadata">

**Author:** ![Anders\_Gregow](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/anders_gregow/32/61721_2.png) [@Anders\_Gregow](https://community.homey.app/u/Anders_Gregow)\
**Post date:** [January 12, 2026, 2:47pm UTC](https://community.homey.app/t/monitoring-or-logging-errors-in-devices/149106/2 "2026-01-12T14:47:25Z")

</div>

I guess the warning is “device not available”?  
The app Device capabilities has a card for this; triggers when a device becomes unavailable.

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [January 12, 2026, 3:13pm UTC](https://community.homey.app/t/monitoring-or-logging-errors-in-devices/149106/3 "2026-01-12T15:13:40Z")

</div>

In order to reveil the cause, maybe the [Audit app](https://community.homey.app/t/app-pro-audit-adds-logging-and-tracing-to-your-homey-pro-and-integrates-into-third-party-systems/101554) can tell you more.

But the most common causes are

- some connection issue (wifi, LAN, internet, manufacturer’s API a.k.a. “the cloud”, zigbee, z-wave, Matter)
- app issue (crashed, or paused by Homey because of excessive memory of CPU usage, or disabled by a flow you once created)

---

<div class="post-metadata">

**Author:** ![Johan\_Taal](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/johan_taal/32/9807_2.png) [@Johan\_Taal](https://community.homey.app/u/Johan_Taal)\
**Post date:** [January 12, 2026, 3:47pm UTC](https://community.homey.app/t/monitoring-or-logging-errors-in-devices/149106/4 "2026-01-12T15:47:36Z")

</div>

Thanks. I Will try this app.

---

<div class="post-metadata">

**Author:** ![Johan\_Taal](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/johan_taal/32/9807_2.png) [@Johan\_Taal](https://community.homey.app/u/Johan_Taal)\
**Post date:** [January 12, 2026, 3:48pm UTC](https://community.homey.app/t/monitoring-or-logging-errors-in-devices/149106/5 "2026-01-12T15:48:10Z")

</div>

Thanks. I Will try this app too.