Can we have a flow in Dev tools where where all these 3 items are on the same page?
I have to bounce back and forth after making a change to check config, read logs and then restart or reload a config item.
Why do you even need those? To me, that is a more interesting question.
As in, “check config” before doing a “restart” (for example), it is quite unneeded. As a restart already checks the config by itself (and will abort the restart if it didn’t pass).
…/Frenck
I use “check config” so I can find errors in the logs and fix them before a restart or before reloading templates etc etc.
Edit: to clarify, the errors are typically typos or simple errors in my template sensors etc etc. I do as much as I can in yaml as I enjoy it that way.
But pressing restart already checks the config… so you are doing an duplicate and unneeded handling there… (that was the point I was trying to make)
Not* all errors in the logs prevent a restart, I’d like to know what errors I can fix (and fix them) before reloading or restarting.
Edit: …and restarting isn’t always the objective, more often it is reloading a config group (eg: template sensors).
A good place to also have ‘read logs’, for example, would be dev tools > yaml above the reloading section. …then everything is together.