Yes, but what you aren’t understanding is that the type of check that you want to run cannot be ran in the running home assistant. So all that config check can do is validate the yaml. It’s literally impossible for config check to find that issue. That’s why the SSH config check exists so that it can spool up a running home assistant process to do a full validation. I’m 99% sure this has been explained to you multiple times.
As it is right now currently in the system, HA knows:
- that there is a problem with an automation and that the automation needs to be disabled. it even knows which automation it is.
- it prints a notification in the homeassistant.log file of that action of disabling of the erroneous automation. and it reports which automation it is by name in the log as well.
both of those things happen with just a reloading of automations and doesn’t require a restart to find the problem and report it in the log.
based on those two things it shouldn’t be too technically challenging to also just put a persistent notification telling the user that there is an issue.
prior to the rework it would just disable all automations instead of just the problematic one so that part is better in that it only disables the offending automation.
but also before it would tell the user that all automations were disabled and direct them to the log to see what the issue was. The way it is now is a step back in user friendliness and functionality.
1 Like
Yes, you’re right, it requires a reload, which check config does not do. Hope you understand now. It’s impossible to catch what reload does with check config without reloading. Hence why the SSH check config spools up a new instance of HA to generate the errors that reloading produces without impacting the currently running system.
And that has nothing to do with what I was explaining, at all. I was explaining because you said these comments about check config.
So to recap: The check config button cannot do what you want. It is a technical limitation. That’s it. Reloading can. Yes a message would be nice. I’m fairly sure it was just forgotten. But by all means, continue to think it was done maliciously, I don’t expect any less from you.
@c0ntax: since the problem you had is solved, please take the time to mark the answer as solution, you do that by selecting the three dots under the post:
Then select the check box:
Don’t forget too while you’re down there to click the heart to like the post, as a way of saying thank you.
1 Like
No problem @Nick4 I was going to do that, I was just watching the other part of the thread unfold 
1 Like