# \[REQUEST\] Provide default flow & sensor logging

**URL:** <https://community.homey.app/t/request-provide-default-flow-sensor-logging/41599>\
**Category:** Ideas & Suggestions\
**Tags:** flow\
**Created:** [January 22, 2021, 12:36pm UTC](https://community.homey.app/t/request-provide-default-flow-sensor-logging/41599 "2021-01-22T12:36:31Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![JeeHaa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jeehaa/32/29849_2.png) [@JeeHaa](https://community.homey.app/u/JeeHaa)\
**Post date:** [January 22, 2021, 12:36pm UTC](https://community.homey.app/t/request-provide-default-flow-sensor-logging/41599/1 "2021-01-22T12:36:31Z")

</div>

The #1 troubleshooting tool is completely missing from Homey: decent built-in logging to get an idea what is going on with flows & devices! I know there are very useful apps out there that fill the gap to a certain degree, but to be honest this is core functionality that should be provided by Homey. I think it might even save time for Athom support, because it would help us troubleshoot certain scenarios ourselves. In some cases all I could do was file a support request with Athom and add a diags dump for them to inspect. When a flow fails intermittently, there is no way for us to find out which “card” and/or device failed. And it certainly would help with Flow editing in general!

I understand this should not be debug level logging for everything that is going on for obvious performance reasons, but it should at least provide an option to log flow start/fail events and device updates. It could be a per-flow setting with different log levels.

Suggestions:

1. Option to set Log Level (at least Flow Start + Result): per Flow or All Flows
2. Option for (zigbee) device logging: per Device/All devices
3. Generic system events log?

---

<div class="post-metadata">

**Author:** ![DirkG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dirkg/32/118897_2.png) [@DirkG](https://community.homey.app/u/DirkG)\
**Post date:** [January 22, 2021, 2:05pm UTC](https://community.homey.app/t/request-provide-default-flow-sensor-logging/41599/2 "2021-01-22T14:05:16Z")

</div>

Agree, +1

---

<div class="post-metadata">

**Author:** ![Andres\_Moerland](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/andres_moerland/32/33756_2.png) [@Andres\_Moerland](https://community.homey.app/u/Andres_Moerland)\
**Post date:** [January 22, 2021, 3:02pm UTC](https://community.homey.app/t/request-provide-default-flow-sensor-logging/41599/3 "2021-01-22T15:02:31Z")

</div>

Would love that!  
+1

---

<div class="post-metadata">

**Author:** ![Shakesbeard](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/shakesbeard/32/15112_2.png) [@Shakesbeard](https://community.homey.app/u/Shakesbeard)\
**Post date:** [January 22, 2021, 4:18pm UTC](https://community.homey.app/t/request-provide-default-flow-sensor-logging/41599/4 "2021-01-22T16:18:32Z")

</div>

+10

---

<div class="post-metadata">

**Author:** ![Henk\_Renting](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/henk_renting/32/87634_2.png) [@Henk\_Renting](https://community.homey.app/u/Henk_Renting)\
**Post date:** [January 22, 2021, 8:19pm UTC](https://community.homey.app/t/request-provide-default-flow-sensor-logging/41599/5 "2021-01-22T20:19:36Z")

</div>

Agree.  
Although I think the logging apps do a very nice job too.  
Would rather have Athom concentrate on things that aren’t already provided by 3rd parties.  
Like a decent dashboard.  
Or the new v5 firmware… 🙂

---

<div class="post-metadata">

**Author:** ![FKey](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/fkey/32/14793_2.png) [@FKey](https://community.homey.app/u/FKey)\
**Post date:** [January 22, 2021, 9:46pm UTC](https://community.homey.app/t/request-provide-default-flow-sensor-logging/41599/6 "2021-01-22T21:46:39Z")

</div>

Oh yes,  
I have papertrails in every flow now.  
Should not be required.  
Definitely a big miss

Added a ♥

---

<div class="post-metadata">

**Author:** ![Marcel\_Visser](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/marcel_visser/32/66024_2.png) [@Marcel\_Visser](https://community.homey.app/u/Marcel_Visser)\
**Post date:** [January 22, 2021, 10:44pm UTC](https://community.homey.app/t/request-provide-default-flow-sensor-logging/41599/7 "2021-01-22T22:44:29Z")

</div>

Agree +1

---

<div class="post-metadata">

**Author:** ![Sharkys](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sharkys/32/54029_2.png) [@Sharkys](https://community.homey.app/u/Sharkys)\
**Post date:** [April 6, 2021, 11:03am UTC](https://community.homey.app/t/request-provide-default-flow-sensor-logging/41599/8 "2021-04-06T11:03:58Z")

</div>

+1 …would be great Experimental function !

---

<div class="post-metadata">

**Author:** ![Jamie](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jamie/32/5274_2.png) [@Jamie](https://community.homey.app/u/Jamie)\
**Post date:** [January 16, 2023, 12:46am UTC](https://community.homey.app/t/request-provide-default-flow-sensor-logging/41599/9 "2023-01-16T00:46:41Z")

</div>

+1

---

<div class="post-metadata">

**Author:** ![Chuck](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/chuck/32/146201_2.png) [@Chuck](https://community.homey.app/u/Chuck)\
**Post date:** [August 30, 2026, 10:39pm UTC](https://community.homey.app/t/request-provide-default-flow-sensor-logging/41599/10 "2026-08-30T22:39:37Z")

</div>

+1

I request this also.

If nothing else please provide the ability to log stack traces. Knowing which flow called a common flow can help you understand why the flow was called.
