I don’t know how much this will resonate with people. Blueprints have really helped my automation game. No longer do I have to have “what happens when someone enters” be a separate automation from “what happens when someone exits”. Stuff like that. Amazing.
However the whole discovery experience is very “developer UX”. It should be a first party solution and not a bolt-on of the forums.
I will describe to you, however, my experience searching for Blueprints the first time.
Click on “Import Blueprint”. Internal monologue: I hope there is a way to find blueprints in this import thing. I don’t know how to import something, but we will see.
Presented with “Blueprint Address”. Me: Ok, I don’t know the address? Blueprints have addresses? AHA! There is a “view blueprints on the community forum!”
Arrive at the forums. Me: Ok, this looks like a list of blueprints. I don’t care about any of these. How do I search? Are there categories? Aha, a search button.
Search for “motion light”. Me: Ok, why am I getting results that aren’t blueprints? Did I do something wrong? Aha, if I click on search there is a “In Blueprints Exchange” option. Try again.
Click on any blueprint listing. Me: Ok, each post is completely different. Where is the download link? What is the short description / long description / implementation details. Some people document the journey of their development. Some people post almost nothing. Sometimes the download link is in a reply, sometimes in the original post. Sometimes there is no link and it’s just the code.
Madness. I didn’t even get into the inconsistency of bringing in blueprints, the versioning story, etc. This needs investment - it is one of the most powerful parts of Home Assistant and it’s terribly difficult to use and I suspect lots of people aren’t using it because of that.
The experience should be a first-party discovery UI with consistent places to find certain data (like in Add-ons) and discovery / import should be one cohesive experience instead of two separate things.