I have tried to use blueprints quite a few times but they never seem to be quite right, whilst the point of them is to be flexible, they are often too specific. for example, a blueprint to turn off a climate control when a window is open. Whilst this may be the exact logic I am looking for, what happens if I want to turn two climate controls off when a door is open. I can not, the blue print specifies a single climate control and a window class sensor.
I think blueprints would be even more useful if there was an option in the UI to be able to turn them back into automations, keeping the original logic, but gaining back full control enabling full customisation in the UI again. It would still be making short work, importing the logic, but giving users even more ability to customise. At present the actual blueprint has to be edited in yaml, then once that is done the blueprint has to be added as an automation and then the various entities selected.