Building the device database together: Public preview now live – Open Home Foundation

Ever since we introduced the idea of a community-powered device database at State of the Open Home 2025, our goal has been clear: create a “Wikipedia of smart home devices” based on real-world usage. In February, we took the first step by inviting Home Assistant users to voluntarily share anonymized device data to help us build it.

Back then, we said we wouldn’t hide behind closed doors until we’d polished some “perfect” final product, and we meant it. At the Open Home Foundation we build in the open. That means sharing our process, our progress, and every milestone along the way with the community that makes it all possible.

So today I’m excited to share the next milestone. The seeds we planted in February have started to sprout: thanks to the incredible response from thousands of users who opted to share anonymized device data during the initial phase, the preview edition of the database’s public interface is now live!

What is the preview edition?

Providing a public, open way to browse the anonymous, aggregated device data we collect was always part of the plan, and this preview is our first step toward it.

You can already use it to search and filter devices to see aggregated community insights, starting with a deliberately focused set of specifics, such as whether a device requires an internet connection, and which protocols and integrations it works with. We’ve kept that initial scope narrow on purpose, giving us a solid foundation we can build on together with you, our community, as the database grows.

What you see today is only a slice of what’s to come, and we want to be upfront about that. Yes it’s functional, but it’s unpolished. There are no final design flourishes, and we’re sure there are a few bugs waiting to be discovered. We don’t even have an official name for it… yet. But we’d rather you experience it now than wait for the full picture before opening the doors.

So please, jump right in.

Help us test it

This is a resource built by the community, for the community, so we want you to start using it now. The more you explore it today, the more powerful we can make the official launch later this year.

It’s the baseline everything else builds on, where you can browse, search, and read device data, and it’s the groundwork for the richer pages and community contributions still to come.

As you explore the preview, we’d love your help tracking down areas where we can improve. We’ve set up a dedicated feedback channel on Discord, and that’s the best place to share your thoughts so everything lands in one spot. A few things we’re especially keen to hear about:

  • What’s missing for you: Which device details would help you make a decision, and what extra features or information would make the database more valuable to you?
  • Interface usability: How easy is it to navigate, search, and make sense of device information, and did you hit any hurdles or confusing moments along the way?

Big reactions or small ideas, what you’d keep or what you’d change: all of it helps. Head over to the discussion and let us know what you think.

A couple of things you might notice along the way:

Can’t find a specific device? To ensure data quality and accuracy, devices only appear in search results once enough independent submissions have been aggregated and validated. Additionally, during this early phase, custom integrations and service-type devices are not yet included.

Want to edit or add device details directly? Direct contributions to device pages, like adding context or correcting details, are firmly on our roadmap but a little further down the line. Right now the focus is simply making the data collected so far accessible and useful to everyone.

So for now, take it for a spin and let us know what you think. Like I said back in February, this is a marathon, not a sprint, and your feedback will directly shape the final product!

Explore the preview

Share your feedback


This is a companion discussion topic for the original entry at https://www.openhomefoundation.org/blog/building-the-device-database-together/
3 Likes

I don’t use Discord so I’ll add some feedback here. This is great! Some consolidation is needed on the different manufacturers, example:

6 Likes

The device database is a fantastic idea, nice to see it lift off.

Discord is a terrible place for feedback and discussions. Please consider alternatives in the future.

1 Like
  1. There should be some explaiantion for each device what it is - at least some link.
  2. Adding images would be an great idea
  3. Also i am sure that Tapo RV30 Max can be set up other than Matter
  4. The database should also tell what entities can the device expose - so e.g. i can see tha tatpo S200B will not tell me when it is tapped
  5. Tapo T115 is missing as well as Tapo T315
  6. Some names like lumi.weather are propably not corrent
  7. I do not use discord so i write feedback here

They’re correct. Lumi = Aqara. Lumi.weather is their old T&H sensor.

2 Likes

Are you sure about those last 2? I don’t see protocols mentioned anywhere on the device page, and integrationS seems to be limited to a single entry.

Take the Shelly 2PM Gen4 as an example. It supports Wi-Fi, Zigbee, Matter & Bluetooth protocols, but the device page doesn’t say that. It also only lists Integration: Shelly, when this device can be integrated under Shelly, ZHA, Z2M, Thread & Bluetooth (and probably more integrations like Deconz).

Even the device category is incorrectly listed as Networking. Guess it’s a networking device because it uses wifi? Should we just ignore it’s main purpose of power monitoring & control?

PS - might be a good idea to add the protocols and integrations filters on the main page once the above is sorted out. Most people will search by protocol+function first when looking at buying a device.

3 Likes

[No Discord for me due to valuing my privacy and autonomy]

I tried some searches:

  • “Lawn” brought up things like awning. Perhaps if there aren’t exact matches it gets fuzzy, which is ok, but maybe keywords for types of device would help.
  • “Lawnmower” gave no results (see above re keywords)
  • “mower” gives 24 identical results (Automower). I didn’t check them all but they appear to be for different model numbers, but to find that you have to open the item and scroll to the bottom. I think the model needs to be in the list of results and at the top of the info page.
  • also these Automower devices appear to be in the category “Networking” which I think must be wrong.
  • I second the suggestion for a link in the listing that takes you to device specific information or at least the manufacturers website.

Was Generative AI used to help populate the database? Those errors look typically non-human.

So a brilliant resource which as you say is not yet polished.

2 Likes

I searched for “plug zigbee” to see if my third really plugs were listed.

They were not. Searched for “reality” and the results contained my plug’s model number only.

Needs curation.. hope I can help.

Would be nice to be able to search for plug or socket and the be able to refine by Wi-Fi , Z-Wave, Zigbee etc.

Oddly, most, if not all plugs were categorized as networking. I would suggest that right off the bat that the data should be analysed by an informed model to suggest more appropriate categories.

1 Like
  • What’s missing for you: Which device details would help you make a decision, and what extra features or information would make the database more valuable to you?

As this backlog item, please look into how and if could add extended additional metadata information about device’s specifications in the devices database → Additional extra metadata information about device's specifications in the devices database? · OHF-Device-Database · Discussion #149 · GitHub

I believe that being able to find, filter and sort by such extra product-data would especially to make it more useful when doing pre-purchase research:

Well i would still say that is incorrectly listed in the database as it is right now, because I think that the database should list it by the proper product name an the brand, but that “lumi.weather” is actually only the Zigbee ID that is just taken from the Zigbee firmware which is often not the proper product name or brand. It this case Aqara is really the brand, not Lumi, and the product was never marketed as Lumi Weather. Better to look at Blakadder’s Zigbee device database for product name reference → Aqara Temperature, Humidity and Pressure Sensor WSDCGQ11LM Zigbee compatibility

So I think if have simply scraped users entities then many if not most entries will need to be manually updated to show the correct brand and product name how it was marketed, because the ID and other metadata that was automatically picked up from the firmware will almost certainly not be the correct.

As mentioned by others, all the brands and manufacturers listings also needs to be remapped and consolidated.

Again, for a somewhat better reference for how to list by product name (which is also far from perfect) look at Blakadder’s Zigbee device database for product name reference → https://zigbee.blakadder.com

2 Likes