About the numbers in the integrations directory
The install counts in this directory come from the opt-in analytics that Home Assistant installs choose to share, so real use is higher than any count shown. Every install count comes from that same pool, which is why the ranking still holds. This page says what each number means, where it comes from and how fresh it is.
What an install count means
An install count is the number of Home Assistant installs that turned on analytics and reported the entry. Analytics is opt-in, and sharing which integrations are in use is a second opt-in on top, so the true number of installs is higher. The directory words every such number as installs sharing analytics, never as a count of households or people.
Every entry with an install count is counted from the same pool, so one ranking above another is a fair comparison even though no count is complete. Dashboard cards and themes send no analytics at all. They show GitHub stars instead, and are ranked by stars among themselves.
Where each field comes from
- Installs for built-in integrations come from Home Assistant analytics: built-in integrations.
- Installs for custom integrations in the Marketplace come from Home Assistant analytics: custom integrations.
- Installs for apps come from Home Assistant analytics: apps.
- The name, type, config flow, local or cloud and brand groups of a built-in integration come from the Home Assistant integration catalog.
- The quality scale tier and the entity types a built-in integration provides come from Home Assistant core code, read from each integration's own files.
- A built-in integration's own texts come from the Home Assistant release on PyPI (setup texts), read from its translation files.
- The lists of Marketplace integrations, dashboard cards and themes come from Marketplace catalog: integrations, Marketplace catalog: dashboard cards and Marketplace catalog: themes, in that order. Each names repositories only.
- Which repositories were taken out of the Marketplace, with the reason given, comes from Marketplace catalog: removed repositories.
- The description, stars, latest version, last update and archived flag of a Marketplace repository come from GitHub.
- For a Marketplace integration, the domain, local or cloud and the entity types it provides are also read from its repository on GitHub, from its manifest and files.
- What an app is called and what it does come from App repositories, read from the config files of the most used app repositories on GitHub.
- The Open in My Home Assistant links are built from the entry's domain or repository, and no text from home-assistant.io is copied.
Categories
A built-in integration takes the first category Home Assistant lists in its code, where it lists one. Every other entry follows the directory's own rules: it is placed by its name, else the kinds of device it adds, else its description.
An integration is listed under its main category only, so no list repeats it. Dashboard cards, themes and apps are listed under none, and neither are integrations that fit no category or that Home Assistant sets up by itself.
A category with 5 entries or more gets a page of its own, ranked by installs sharing analytics. The smaller ones are named on the categories page with their counts.
Screenshots
The screenshots of Marketplace integrations, dashboard cards and themes are copied from each project's own README, up to three per entry. Each one carries a credit to its repository and a link back to where it was found, and belongs to its author.
They are served from vulpo.app, so a visitor's browser never contacts GitHub to show them. To have a screenshot, or every image of a repository, removed, ask through the contact page at /contact. It goes onto a list that every later update honours, so it does not come back.
Icons
Logos and icons belong to their owners and are shown only to identify each entry. The icons of built-in and Marketplace integrations come from the Home Assistant brands repository, an app's from its own repository, and a dashboard card's or theme's is cut from its first screenshot.
Like the screenshots, they are served from vulpo.app, and one is removed on request through the contact page at /contact.
Descriptions
Each description is an automatic summary, written by Claude, an AI model made by Anthropic, from the entry's own sources: Home Assistant's source code for a built-in integration, and the code and README of the project for everything else. A README is used only when its licence allows reuse. Home Assistant's documentation is never used. Before a description is published, rules check that it names only things its sources contain and that it never claims to be official. Nobody reviews each one by hand, so a mistake can slip through. To report one, use the contact page at /contact. A project's maintainer can send their own text the same way, and it replaces the summary.
Setup texts, entities and actions
On a built-in integration's page, the setup fields, entity names, actions and repair notices are Home Assistant's own texts, read from its release on PyPI under the Apache License 2.0. A Marketplace integration's come from its own repository. Where a repository has no licence that allows reuse, only their names are shown.
README excerpts
A Marketplace entry's or app's page can quote the start of its README or docs and its feature list, shortened and without images or formatting, when the repository's licence allows reuse. The quote names the licence and links to the full file. To have an excerpt or a description removed, ask through the contact page at /contact. It goes onto a list that every later update honours.
How often it updates
The data is fetched once a day and the site is rebuilt from it, so a page can be up to a day behind. If a source cannot be reached, the last good data for that source is kept and the table below says so, with the date it is kept from.
The table lists each source, whether its last fetch worked and when the data was last fetched, in UTC.
| Source | Status | Last fetched (UTC) |
|---|---|---|
| Home Assistant analytics: built-in integrations | OK | October 27, 2026, 09:15 UTC |
| Home Assistant analytics: custom integrations | OK | October 27, 2026, 09:15 UTC |
| Home Assistant analytics: apps | OK | October 27, 2026, 09:15 UTC |
| Home Assistant integration catalog | OK | October 27, 2026, 09:15 UTC |
| Home Assistant core code | OK | October 27, 2026, 09:15 UTC |
| Home Assistant release on PyPI (setup texts) | OK | October 27, 2026, 09:15 UTC |
| Marketplace catalog: integrations | OK | October 27, 2026, 09:15 UTC |
| Marketplace catalog: dashboard cards | OK | October 27, 2026, 09:15 UTC |
| Marketplace catalog: themes | OK | October 27, 2026, 09:15 UTC |
| Marketplace catalog: removed repositories | OK | October 27, 2026, 09:15 UTC |
| GitHub | OK | October 27, 2026, 09:15 UTC |
| App repositories | OK | October 27, 2026, 09:15 UTC |
Who makes this
This directory is independent. It is made by the developer of Vulpo, a Home Assistant app for iPhone, iPad and Mac, and is not affiliated with Home Assistant or the Open Home Foundation.
Whether Vulpo supports an entry plays no part in how it is ranked.
Corrections and removals
If a brand is grouped wrongly, an entry sits in the wrong category or a fact is out of date, send it through the contact page at /contact.
Requests to remove a screenshot or an icon go the same way, and each removal is kept on a list that every later update honours.
Excerpts and descriptions can be removed the same way.