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.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
Solved
Homey Log File (are there apps that give more information about flows/triggers)
vaderag
Member
I found a discussion along these lines in the developer section but I'm hoping there is a more user friendly log somewhere that tells me which flows/devices were activated and when?
Sometimes some of my flows don't do quite what they are supposed to and I'd like to establish if this is my flow writing or a device issue...
Thanks
Sometimes some of my flows don't do quite what they are supposed to and I'd like to establish if this is my flow writing or a device issue...
Thanks
Tagged:
Comments
What I learned in the last few days is to add some time delays if you want some things happen with the same trigger. For example, calculate a variable an push it to a phone. You can do both in the same flow but add a 1 second delay for sending de message. Else the message can be send before the calculation is done.
Re the insights tab, all I see is the memory usage at the top and that's it
I also replied above that I looked in insights and saw nothing but memory usage? What more would you like to see in terms of what I tried?!
I appreciate you advising me to look on the app store, and that answers my question, but why should it be assumed that logging would be done by an app?
To a newbie like myself the app store is designed to add devices to your homey... it is not a logical place to search for a feature like this - logging is surely base level functionality... on my phone is done by Android, logging on my computer is done by Windows, I would expect logging to be done by the OS, not by some app pasted on top using additional resources...
But great your question has been answered, i will put this topic to solved and change the topic title a bit to make it more search friendly
Homey logger screenshot:
I feel this shouldn't be something that I need to add cards into (in some cases) already pretty complicated then columns... one of the things that sold me on Homey was the elegance and apparent simplicity of the flow editor (which i'm gradually learning is not quite so) compared to other products...
Homey must be sending the commands to devices - it seems that low level what command was sent and by what flow must be happening somewhere and logging that seems a necessity in some way...
I'll play with Homey Logger and see what I get
The other and main issue with that is that you'd need to add log cards to every single action.
Let's use last night's example. I have a flow that turns on a Hue Bulb, a Lightwave Switch and says "reticulating splines" when it happens.
I know it's happening as homey talks and 99% of the time it works as expected. Last night however the Lightwave Switch didn't turn off. I can debug to my heart's content and it works. I don't need a log card as it will only serve the same purpose of the voice.
What I do need is a way to look at what homey did, in that particular instance, to debug whether it got caught up on something so didn't send the command (maybe the status was misread), it did send the command but it wasn't receved etc
That's a simplified example, others are obviously more complex and even harder to debug, but you need a way to see what has happened, posthumously...
https://apps.athom.com/app/gov.nsa.logger
https://apps.athom.com/app/nl.nielsdeklerk.log
https://apps.athom.com/app/nu.dijker.papertrails
also: system-settings-zwave
The main time you want to check what's going on (unless you're a developer) is when something occurs that is not expected and not predictable. All of those solutions require a crystal ball...
I can't see how logging can be an issue - I've seen what's going on using homey logger and it's not crazy amounts - presumably that is all coming from homey core somewhere. It's only a text file!
Otherwise the only thing that is left if above is not a solution is making a logger app that fits your needs.
Is that not using the core to pull that information?
Presumably the standard is for apps to run all the time so could it be forked to do that?
I no longer have the technical skills to do this but I have friends who may be able to help... No point of it's impossible tho
https://apps.athom.com/app/gov.nsa.logger