# 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:** 1\
**Showing post:** 3

<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)

---

_[View the full topic](https://community.homey.app/t/monitoring-or-logging-errors-in-devices/149106)._