How we'll build the device database, together

Imagine knowing how a smart device will actually perform in your home before you buy it… not from a spec sheet, but from anonymized data that people running setups just like yours have opted to share. Having answers to questions like: will this sensor work without the cloud? Is that smart plug actually being reported by users as reliable? Does “local control” mean local always, or just sometimes? Will these devices work well across protocols? What this device looks like in other users’ homes?

That’s the idea behind the Open Home Foundation Device Database: a community-powered resource built from anonymized data shared voluntarily by Home Assistant users around the world. The aim: to give people the information they need to benefit from privacy, choice, and sustainability in their smart homes.

Having easy access to this wealth of data changes everything. With the device database at your fingertips, you’ll know upfront that there are 1000+ Home Assistant users running that smart plug fully locally, and it includes those voltage and wattage sensors you were looking for. Or if you see a sensor everyone’s raving about requires Bluetooth when your protocol of choice is Zigbee, the database could save you the hassle of buying it in the first place.

Of course, there are some excellent device databases and compatibility lists already available. Our own Works with Home Assistant (WWHA) program puts products through their paces in home settings, which has taught us how vital real-world testing is. But to really understand how devices perform across the incredibly diverse range of setups out there (different integrations, hardware combinations, network connections, and protocols) we need data at a much larger scale. That’s what makes the device database different: it’s thousands of real homes opting in to contribute real anonymized data. And that’s only possible with your help.

Building together

Creating the device database is a big job, and we’re going to need your help to do it. Before we build a shiny new website or complex search engine, the first step is to make sure the data you opt to share with us is accurate, anonymized, and meaningful, so we’re prioritizing:

  • Privacy first: The information we collect strictly follows our privacy principles: we don’t collect any personal data, period. Instead, we only share aggregated versions of device data, ensuring our community gets the insights they need without compromising anyone’s privacy. Check out our Data Use Statement for details.
  • Real-world context: Our device database is centered around anonymized device data from Home Assistant instances of users who choose to participate through this new Labs feature.
  • Laying the groundwork: To prepare the first stage of this initiative, we invited members of the Open Home Foundation, our commercial partners, and a range of Home Assistant users, to opt into sharing their device data with us. This collaborative start has helped us aggregate more than 2,000 unique devices across more than 160 integrations, with lots more to come.
  • Transparency: We’ve launched an initial public dashboard for aggregated statistics and data downloads, giving you a first look at the insights as they grow. Of course, we won’t stop there, as we’re approaching this step-by-step…

Nothing happens overnight

Like everything we do, the Device database initiative follows a steady, iterative approach, which takes time. We want to be honest: nothing happens overnight. We don’t believe in hiding away for years behind closed doors just to launch our vision of a “perfect” finished product (spoiler: there’s no such thing as perfect!). Instead, in the true open source fashion, we build in the open, release early experiments, and refine them based on how our community actually uses them.

Right now, in these early stages, our focus is on planting the seeds and gathering the first shoots of real-world information, as well as your feedback. This way, the tools we build later can grow and evolve alongside your needs.

The next steps

Following our iterative philosophy, we have a roadmap of small, manageable milestones designed to gather feedback at every step:

1. Launching in Home Assistant Labs

We are introducing the Open Home Foundation device database as a Labs feature in the 2026.2 release of Home Assistant. The idea is to broaden visibility and reach a wider audience (hello, that means you 👋) willing to contribute by opting in to share their device data and providing valuable feedback.

2. Putting the data in your hands

Building on the further insights and feedback we gather, we’re planning to launch the first public device database web interface in the first half of 2026. The plan is to make it easier for you to explore and interact with the information, beyond simple statistical dashboards.

While this initial version will be far from the final version (if there ever is one!). By getting it into your hands as early as possible, we can better understand where to go next, and make sure our future work is focused on the most valuable features for you.

3. Encouraging community contributions

Right from the start, we’re establishing simple flows to enable you to contribute more easily, allowing you to enrich the device database by adding real-world insights, all under the watch of our community. The result: an authentic and unbiased source of truth that helps everyone make informed decisions when it comes to privacy, choice, and sustainability in the smart home.

Now it’s over to you!

Because this project belongs to the community, we need your perspective early and often to help shape what comes next.

This is a marathon, not a sprint. The device database will only become a definitive resource through consistent, collective effort over the coming months and years, but bit by bit, device by device, we can make something great together! Here’s how you can be part of it:

  • Enable Device Analytics: If you use Home Assistant, opting into Device Analytics in the Labs menu is the direct way to contribute to the device database.
  • Provide feedback: We’ve created a simple survey form so you can let us know what you think of the initiative, and why you’d like to contribute (or not!).
  • Join the discussion: We also have a dedicated Discord channel and want to hear what matters most to you: how can we make the device database a flourishing resource the community can trust for years to come?

Together we’ll build a transparent, open, and community-driven map of the real-world smart home ecosystem: one that gets better with every contribution. We hope you’ll be part of it.


This is a companion discussion topic for the original entry at https://www.home-assistant.io/blog/2026/02/02/about-device-database
11 Likes

Ok, nice. At first glance everything looks clear or does it ?

Ok we want to know does eWeLight model ZB-RGBCW works with ha and is it local only.

But does this device database include ie. routers that are integrated in ha? Because now days router is not any more just a some network device stuck on shelf somewhere. It can be smart device in your smart home eco system too.

And if routers are part of this how will you know? Maybe stupid question but I’m using openwrt and opnsense on them and it doesn’t have much to do with manufacturer of device as they are running different firmware.

Or another example. i have asecam 5m ptz poe camera that doesn’t have any integration. It is used by frigate, no cloud, no services, nothing. it just work as local camera. It will probably never show up in devices work with home assistant.

Was this meant to be published before 2026.02 is available?

I would guess yes to make people aware before.

Beta is also out

Release will be soon. I read Wednesday somewhere I think and started to believe there is actually a schedule.

And I found the schedule

Alright, I thought it just a bit weird, because for example the Survey asks that you have the update installed. I thought maybe someone just clicked publish too early.

I hope the database is designed to handle devices that can be connected multiple ways.

IE will mqtt zigbee2mqtt devices be collected as zigbee the same way as zha connected?

Or what about devices that can be connected via bluetooth or API or matter?

Hopefully there will be some association / deduplication.

2 Likes

Excited to see this and contribute where I can!

Hopefully if done right this could be a very powerful tool for understanding how to better use devices and make buying decisions - I loathe buying devices only to find out later they’re kinda rubbish…

Would be great to see things like understand if X device is actually a rubbish Zigbee router and should be avoided, or if Y device can actually be flashed with better firmware to make it local only etc.

1 Like

MQTT devices aren’t collected at the moment (at least in the latest beta), it might change in the future.

It seems that this is targeting core, native Home Assistant integrations for now.

That seems like a reasonable way to start, but I hope it doesn’t stay that way. It is being billed as the “Open Home Foundation Device Database” not the “Home Assistant Device Database”, after all. I’m an enthusiastic Home Assistant user but I would prefer to contribute to something that wasn’t explicitly (or implicitly) tied to one platform only.

1 Like

This sort of thing is a fine line for many users.

They want to keep their data private but they also want to contribute.

This requires trust in the platform, which I think Open Home Foundation has built through consistent transparency and clear intent / actions over a long period.

I never think “does this creepy tech company want to monetise my data”?

Nice work all.

Any chance you could take more inspiration from Zigbee2MQTT’s device database for the web interface of this ”Open Home Foundation Device Database” and allow a lot more information about each device for better context and end-user support?

Some of Z2M’s pages for Zigbee devices for example also contain a few basic but vital usage information that most users need, like how to factory reset that specific device and how to put it into pairing-mode in order to enable joining, all of which is key to allow commisioning a device if do not have access to its user manual.

4 Likes

The problem with this is that it can easily backfire.
As home assistant popularity grows, and we are dealing with companies, it could easily end up like this.

This is 50% more because it is working with home assistant.

No, it doesnt have to work with home assistant. It has to work with gnu/linux.

And then it is the whole new ball game.

Isn’t this what the Quality scale is for?

Yes, however there are so many devices it is impossible to test everything fully ‘in a lab’ so this way the community will provide information on what works and what doesn’t.
Edit, or were you answering to Daniel?

Would you consider exposing and providing an official and public or private MCP (Model Context Protocol) server to let external AI models access this database as a data source which anyone can use directly?

Perhaps also have offer optional versioned release copies of the database be available as an app/addon that can be installed in Home Assistant Operating System so that a local copy can be exposed and accessed locally in an way via Home Assistant’s built-in MCP server integration?

Regardless it would be very useful if Home Assistant’s user could could enable AI models (like Claude or ChatGPT) to access this database and exposing via MCP servers as that is now the standard for how AI can interacts with data such as this, and the point is that it should be easy for an AI model to access this database in a standardized way.

As long as the dB can be hit we (anyone who knows MCP) can make an MCP server H. I wouldn’t worry too much about that.

Where can I find this device database? Is there a link in the article I overlooked?

1 Like

It is not made public yet, and that is stated in the article:

  • we’re planning to launch the first public device database web interface in the first half of 2026.

They only share statistics so far as a first step (and as a teaser):

There is some more info in the upcoming relase notes (now in beta):

The true power of this database isn’t about the devices; it lies in how devices are linked to triggers and automations by the broader community. This will allow Home Assistant to suggest automations to new users based on the devices they have in their environment. Take advantage of “Hive mind” and reduce the “blank page” problem when getting started. Very smart, really. Good long-term thinking.

2 Likes

No, the quality scale grades the overall quality of an integration based on a few key metrics. Integrations connect devices to HASS, so judging the quality of an integration is very different to that of the device(s) that an integration may happen to serve.

1 Like