Blueprint analytics

Feature Requests
1

I am currently researching most used blueprints, and I realized HA has an awesome website about addons and integration usages. Would be excellent to add also the most used blueprints in the same fashion.

This would guide the users on blueprint usage and make the experience smoother. Today there are some resources already:

Still a bit daunting to go through. analytics of home-assistant offers a much better visualization overall.

2

The HA analytics are driven by an opt-in in the HA software itself.
Blueprints are written by random people such as myself and are not affiliated with HA at all.
Just like EPMatt is also not HA.

I have no idea what you are asking to here. but it does not appear to be related to HA at all.

3

Dear @Sir_Goodenough you are right about how both work. Both are components to HA. My suggestion is that the analytics also collects blueprints from community users are using in HA. Integrations work in a a very similar way when you check.

The benefit is that the community looking for blueprints would also have a ranking of most used blueprints to decide what to do.

4

Except that blueprints are just code. The code is referenced by automatons, scripts, or templates to do things. Does it get counted 10 times because you are using the blueprint for 10 different script calls?

It doesn’t really make any sense. It is also not HA code, and that is the real issue. You will notice Custom Integrations are also not referenced because, wait for it, they are not HA code either…

5

No it does not count 10 times when you use 10 times. The idea is having the list of imported blueprints, so each blueprint imported via blueprint exchange would count 1 time per HA installation.

Same idea when you have 10 devices on Matter integration. It will count you have 1 Matter integration in your installation.

6

What if you write your own blueprint. What if it only exists on GitHub.

And don’t forget the policy problem…

7

@Sir_Goodenough actually Custom Integrations would fit in the same proposal of this request. Let me dig deeper in what I would imagine:

  • addition of analytics for custom integrations and blueprints to give users visibility into which ones are being used most frequently.

  • Implementation Suggestion:

  • Utilizing the same opt-in telemetry system for custom integrations and blueprints.

  • Leveraging GitHub API or Home Assistant forums for blueprint analytics.

  • Ensure privacy and anonymity with data collection.

Benefits of the Feature:

  • Better visibility for developers: Custom integration and blueprint developers would gain insight into how widely their work is being used, which can motivate further contributions and improvements.
  • Community-driven discovery: It would make it easier for Home Assistant users to discover the most popular and reliable custom integrations and blueprints.
  • More informed decisions: Users could more easily choose which custom integrations or blueprints to try based on popularity and community feedback.

While there are challenges, particularly with tracking custom integrations that are less standardized than official ones, this feature could provide great value for the Home Assistant community. Since Home Assistant is community-driven and open-source, requesting this feature is certainly worth considering, and it could be a great way for the developers to further enhance the platform’s utility and collaboration.