This is the forum archive of Homey. For more information about Homey, visit the Official Homey website.

The Homey Community has been moved to https://community.athom.com.

This forum is now read-only for archive purposes.

How to identify cpu draining flows (or processes)

Is it possible to see how much Homey is stressed?

Reason for me asking this, is because I accidentally discovered an error in a flow; it was looping. I couldn't get the flow to work, added a Simple Log card with a comment in the THAN column which made me see the looping flow.

Perhaps I have other errors in flows too?

Is it possible to see the load that flows have on Homey and if it is looping?

Comments

  • Hi Eternity, 
    I think it is not possible to see the load (CPU impact) of a flow at the moment. Only just the way it triggers like you did with a logging card.

    For generic performance I advice the Homey Logger that can log at intervals to it's own insights. 
    For the load from an App you could view realtime in the Developer Dashboard https://developer.athom.com/tools/app-profiling 

    Errors in flows is just not possible, if it isn't broken (App not installed) it just does what you programmed. Maybe that is not what you expected ;-) but that is no error... 

    Connection errors (Zigbee and Z-wave) are maybe in the logs / network graph on the Developer Dashboard.

    I am looking for Adding logging to every flow (if Than of Else is triggered) for my Papertrails App, is that something you would use? Looping of excessive  triggering would be easily visible.

    In the Beta you can also Add logging to the AND Column. (but Logs get large if triggers fire rapidly) 
  • Thanks for the feedback @GeurtDijker

    Yes I made an error an a flow, and Homey perfectly executed the error :-)
    I will have a look at Homey Logger App and Papertrails App. Thanks for the suggestion!
  • Homey Logger does what I ws looking for :-)

    Thanks for pointing me in the right direction!
Sign In or Register to comment.