I would love to have a way to inspect the values during the scripts or the automations.
In my opinion when things are difficult a simple mistake can take hours for being catch.
Having the possibility to write in the automation something like:
LOG_DEBUG: I reached this step but the flag is false or
LOG_INFO: I am here so I will go a step further
would increase the usability of those components.
I don’t know if something like this is possible with the current setup. I googled for a way for debugging an automation but I was unable to find a good way for doing it.
yes, I saw what you was doing in your Repo.
I don’t doubt that it is working. It’s only that you are using what exists now for something different from it’s intended usage. The logbook in my idea should be used for keeping track of what’s happened in the last days.
What I am talking about is some tool that can help you understanding why your automation is not working, or why it is called but it does not reach the end. If we have such tool a person can start developing it’s own automation and when something is not working as expected it can increase the log verbosity and check why it was not working.
At the moment you can increase the log verbosity and see that your automation is called. nothing else. Wouldn’t it be nice have a piece of code that you can include in your automation and that prints something on the log as all the python code that is under the hood?