When writing a blueprint I noticed that HA config check passes even if I have a completely invalid blueprint in my blueprint folder. I did find that if the blueprint you’re writing has invalid syntax then it shows up with an error in the blueprints configuration menu but like this is pretty hard to read:
Is there another way to see this error message in full like you can with a normal config check failure? Or does the CLI have a way to specifically check a blueprint or all your blueprints from there?
I have found that even though a faulty blueprint might pass Check Configuration, executing Reload Automations performs a more thorough check because the mistake appears in Logs.
Interesting. Does that only work if you have turned the blueprint into an automation though? My dev process was:
Write the automation and see it work
Turn it into a blueprint by replacing values hard-coded to me with inputs
Click “create automation” on the blueprint and then test the automation again
So maybe instead I should insert a step where I stub out the blueprint and click create automation ASAP before doing more development. That way I can then check the blueprint’s syntax with a reload automations call?
