#device-database

1 messages · Page 1 of 1 (latest)

valid otter
#

**Welcome everyone to the #device-database feedback channel 👋 **

This channel is about general feedback and discussions on the Open Home Foundation device database.

If you want to engage in the further development and the development community around it please head over to the project channel #1361754948949512203 - where you will need to have a developer or designer role setup in Discord.

For feature requests feel free to create them directly on the Github discussions https://github.com/orgs/OHF-Device-Database/discussions for everyone to easily follow and engage.

We are at an early stage of this exciting journey, so let's aim to shape it together!

simple star
#

where you will need to have a developer role setup in Discord
Or designer 🧑‍🎨 🖌️

cinder tide
#

This seems like an exciting initiative which I think will help device selection immensely, agnostic to the connectivity used.
E.g. if I am looking for a new device I don't care much whether it is thread or zigbee, but I can make an easier comparison across the two.

One question which is not very clear in the announcement...
Is the help you're looking for automated data dumps from HA or manual input? Or do both have their individual place?
The survey talks about prices etc., that's not something HA knows.
The current diagnostics HA gathers are automated in the background, though.

limpid tiger
#

The option to voluntarily donate device data will come as a labs feature in the February HA release.

thorny sluice
#

You can install the 2026.2 beta to enable it before then, though.

stoic briar
#

Are there plans to show mqtt devices as well? I know this could quickly become an unreliable source of spam since everyone can simply add devices via mqtt discovery topics. But I would really love to see all those device metrics from z2m users.

hoary helm
#

I would love if the device database had manuals to the devices

gentle tulip
#

the proposed design has support for external links to documentation, etc. Not hosting the documentation on the site itself, but I'd expect that archive.org links should be acceptable for devices where the manufacturer has taken down the docs :)

true tapir
thorny sluice
#

Yes!

true tapir
solid charm
#

for the interim Grafana website, is there any chance of increasing the page size to > 10? It's super hard to find anything right now. I wanted to try to put the DB to a real world test, I'm looking to buy a roborock. I wanted to see if anyone had reported success with the model I'm looking at. After sorting the integration column I have to page to page 60, a larger page size, or filter/search would be really nice and I know Grafana can do all those things

#

For my real world test though unfortunately either no one has the model I want or the model numbers reported by the integration aren't useful for figuring out the models as named on the roborock website

valid otter
valid otter
valid otter
charred pewter
#

Got official cross-post permission from @thorny sluice 😂

But long story short: I think HA should log (INFO) what it sends to the device DB, just alike how analytics are logged for long time (see example above)

valid otter
wicked quail
#

I really like the idea of building a device database. I believe this would significantly increase Home Assistant adoption by giving users more confidence when purchasing additional sensors and IoT devices.

I use a similar database for OpenWRT, which maintains a comprehensive list of supported devices along with detailed, practical information. That level of detail has proven extremely valuable. For example, their entries often include:

  • Supported firmware and hardware versions
  • Hardware highlights and notes on revisions when vendors change components over time
  • Installation and flashing methods
  • Flash layouts
  • Supported custom firmware options and upgrade instructions
  • Links to stock firmware and official documentation
  • Debricking guides
  • Post-installation tips and tuning recommendations
    I believe a similar structure, combined with community-driven contributions and user responses, could work very well here too.
    Just an example can be seen here: https://openwrt.org/toh/xiaomi/ax3200

This is a fantastic initiative, and I truly appreciate the effort and vision the team is putting into it, keep up the great work!

charred pewter
valid otter
charred pewter
#

Yeah, it was pointed out in #beta moments ago as well. Gave a few thoughts there as well: <#beta message>

valid otter
# wicked quail I really like the idea of building a device database. I believe this would signi...

Thanks @wicked quail for your feedback and welcome 👋

Yes, totally agree. There are multiple database out there covering various aspects, like specific protocols such as Zigbee, Matter or platforms like OpenWRT.

As you mentioned, we're aiming to not just cover the technical compatibility but base it on real-world and community-driven angle right from the beginning. Going forward, we'd love to have conversations of what makes sense to further include to show for devices, like linking to troubleshooting guides, etc.

Did you have a chance to check out the initial design proposal and what we could show for devices? https://github.com/orgs/OHF-Device-Database/discussions/113
That's a good point to further engage, happy to have you onboard 🙂

glacial bluff
#

Having the Device database as a mixture of the OpenWRT hardware database and MusicBrainz 😄 Another source of inspiration could be https://wikidevi.wi-cat.ru/Main_Page, which collects deep technical data of primarily Wi-Fi hardware like routers

valid otter
# glacial bluff Having the Device database as a mixture of the OpenWRT hardware database and Mus...

Good point 🙂
In fact, as also outlined in the discussion of a design proposal (https://github.com/orgs/OHF-Device-Database/discussions/113) we aim to include/reference multiple different external databases/sources to provide a wide view on a devices eventually. Thinking about becoming a Wikipedia of smart home devices it aims to cover a very broad range of devices / protocols / etc.
Would be great to get your suggestions on what sources to include by adding them as a comment to the linked discussion. Thanks!

valid otter
#

As we're now officially launching in Labs as of the 2026.2 release -> What's your bet on how many devices we'll have aggregated until the upcoming "State of the Open Home" in April?
Post them here 👋

PS: We will think of something nice for the winner(s) 🎁

fervent mural
#

100k

valid otter
#

Well I need to top that: 150k 🙂

signal rock
#

I'm on record for 250k

thorny sluice
#

I'm gonna top that, I think there will be half a million in there by SOTOH.

#

We should think of a prize for whoever gets closest. firNodders

misty ermine
#

Obligatory 690k bet from me

winged maple
#

ok, 811.015 for me, what to win here

#

ha is gaining

marble granite
#

101k

valid otter
#

Bet on devices aggregated until "State of the Open Home" in April

limpid tiger
#

1 month of unpaid access to the device database. shksClap dr_evil

glacial bluff
#

Device Database ➕

winged maple
#

passwords and cams included

valid otter
glacial bluff
cold harbor
#

Plus, pro, extra, ultra, pick one 😄

marble granite
#

Device database plus pro max

valid otter
marble granite
valid otter
marble granite
exotic needle
#

one thing I find curious: isy994 is up there in the top 10 devices, while the integration only reports 486 installations. So someone got to have a LOT of them don't they?

valid otter
exotic needle
valid otter
cold harbor
#

I've read that MQTT devices are not included. That leaves out a lot of ZigBee devices 😅

#

Most of my home are ZigBee devices

#

I think maybe you can identify it with some category or label. Otherwise there will be a very partial image, IMHO

valid otter
magic acorn
#

I really like the project to create a device database and the statistics built around it! What would be interesting are trend analysis about absolute/relative numbers of integrations an their development on a timeline. To reduce complexity there could also be an abstraction layer, that clusters only the major home automation standards (Matter, Zigbee, etc.) additional to a more detailed integration view.

valid otter
glacial bluff
marble granite
#

@valid otter do you have the link to grafana? Maybe we can pin it to the channel for easy access

magic acorn
glacial bluff
#

It's a bit sad that the Grafana dashboard is so restricted, impossible to add filters or such

thorny sluice
signal rock
#

gonna be very interesting to see how this chart in particular develops over the months

image.png
valid otter
#

Yes, we're gonna check what's feasible to enhance

charred pewter
#

It also gives a nice indication which HA integrations should get the most love.

I know I know, "All integrations are equal but some are more equal than others" (c) George Orwell 😉

image.png
gentle tulip
#

i suspect there's some very unequal mqtt stuff not included there :)

glacial bluff
glacial bluff
#

We are at over 400 pages in the Grafana table 😄

cold harbor
#

With no ZigBee/ MQTT data, Tuya is King...😅

#

And this with almost no "power user" having Tuya, I'm sure

winged maple
#

ya think tuya?

gentle tulip
#

pretty clear that ikea is driving most of the growth of people using the matter integration.

#

would be neat to see what people are using as thread border routers, but i dunno how that info could be collected :/

cold harbor
gentle tulip
#

The IKEA "Remote Control N2" (STYRBAR) shows up pretty high on the list even without z2m stats included.

valid otter
#

A short update regarding Tuya (and potential other white label products still to be included):

We've changed the manufacturer label from just "Tuya" to "Tuya / Whitelist" in the "Device by Manufacturer" to compensate for that fact that a lot of Tuya devices are in fact stemming from different manufacturers due to the nature of Tuyas white labeling approach.

Furthermore, we're aware that due to the white labeling and thus even having different manufacturers for the same model (e.g. the TS011F) Tuya devices are currently potentially counted multiple times (e.g. _TZ3000_2putqrmw vs. _TZ3000_okaz9tjs).

For now we'll keep the reporting of these devices as-is but of course aim to refine where needed.

Regarding the additional filtering options in Grafana - yeah, as I've stated before that's something we're gonna have a look at. But the team is on a meet-up this week so please be patient a little while longer ❤️

winged maple
shy hare
#

32k unique devices. It’s mental to see how fast it goes

IMG_4169.png
gentle tulip
#

I wonder how much overlap there is between Philips and "Signify Netherlands B.V.", given that current hue stuff is made by signify and uses the signify vendor id over zigbee.

#

oh, huh, seems like some of the "Philips" devices are tvs, via the cast integration.

#

I guess there's a challenge for the device database editing interface - allow devices to be manually associated with a "brand name" that might be different from the vendor id actually used by the product

#

or even multiple brands, for white-label products

#

for matter bridges is it only showing the bridge? or are the bridged devices tracked separately?

acoustic saffron
#

I understand why at a minimum initially including custom integrations wouldn't be on the device database roadmap, but I would hope in the future that custom integration devices could find their way into the database and be marked as "unsupported integration" methods. Some of my most beloved devices are only compatible with home assistant because of the efforts of custom integrators, and I'd love to be able to evangelize them.

It would also be really helpful for developers to see how many different devices/types/users/etc there are for different custom integrations using this data set, so they can both prioritize device support, as well as use it to attract developers to get some of those custom integrations merged into core.

west grove
#

Is there a way to check locally what device data you have sent to the database?

glacial bluff
#

One of my integrations is now showing up, yay :3

image.png
west grove
cold harbor
#

Reeiewing my info...I understand it's hard to retrieve some useful information. I hope it helps 💪

marble granite
valid otter
valid otter
# acoustic saffron I understand why at a minimum initially including custom integrations wouldn't b...

Let's maybe rephrase the "not on the roadmap" a little 🙂 It's basically that they are not considered at the moment to be included right away. But for sure we aim to have a holistic view on devices out there, which also will include custom integrations at a certain point in time. We're just not at the point yet to say it's going to happen until xyz. It's truly awesome to see how many integrations there are apart from the custom ones already. So, we're aiming for it, but let's go step by step here. 👍

fervent mural
#

But also, currently the only thing we have is this upload so it seems super important. It's not. It's only to bootstrap the database. There might come ways to manually add devices to the database, just like we will allow additional metadata to be added via a UI. That's when the true power of the database will show, as right now it's just model names and firmware versions.

#

We want every IoT device in the world included.

#

(in the database, not covered by uploader)

tidal flume
#

I just looked at my analytics preview and some, if not most, of the information is ‘null’. Is there something I can do to change that to add value here?

prisma fjord
#

Where's the analytics preview? I don't remember seeing that

winged maple
marble elk
#

at /config/analytics via the top right three-dots menu

winged maple
#

too

prisma fjord
#

Ah. I thought it was going to be a preview of the data being sent, not the toggles for sending it. 🤣

winged maple
#

3 dots

#

preview

#

downloaded file contains the data that has been send to HA

#

need new keyboard 🙂

prisma fjord
#

I swear I was good at reading comprehension...
Thanks!

cold harbor
#

Also, maybe big companies can see the money they can earn being kind to some sort of tech geeks like most HA users

#

Making their devices local and HA totally compatible

fleet star
glacial bluff
#

Oh no 🙃

image.png
#

Was there already thought of "What happens with models which report different model but the same model_id?" 😄

gentle tulip
#

another fun thing, my two UPSes report their vendors as "APC" and "American Power Conversion"

cold harbor
#

Yes, the data is very dirty

gentle tulip
#

the raw device analytics data is a mess, and there's going to need to be some manual tidying up and merging and linking done to turn it into a useful database.

#

(amusingly, musicbrainz had a kind of similar issue where they allowed direct submission of data from cd rippers via the cddb/freedb protocol - these ended up being turned into "stub" releases that an editor could later use as the basis for a real release to properly link things into the database)

glacial bluff
#

MusicBrainz also has release groups to bundle releases

glacial bluff
#

An interesting topic by the way ^^

gentle tulip
#

yeah, that's to handle stuff like the same release being somewhat different depending on country. Not sure if that directly maps to a device database

#

I guess there are regional device variants like plug type that should be shown together

#

(in some cases, the device analytics might not be able to tell apart regional variants where e.g. a bulb is E26 vs E27 or a socket is american or UK or whatever)

proud parrot
#

Music releases are ridiculous in their global variation

glacial bluff
cold harbor
#

I realised that my Tasmota smartplugs appears as Tuya...

gentle tulip
#

yeah, known issue; Tuya api doesn't provide enough info to easily identify the device's consumer brand.

#

that's why the graph got updated to say "Tuya / Whitelabel"

cold harbor
#

Well, in this case I say Tasmota because is a local and open software, nothing to do with Tuya 😅

gentle tulip
#

hah, Samsung is currently both positions 2 and 3 in the brands list

cold harbor
#

And I keep wondering why there is no ZigBee devices, or the Zigbee2MQTT, AFAIK

gentle tulip
#

mqtt is currently excluded

#

there's lots of zigbee devices from people using zha but they're a bit undercounted

#

note that "Signify Netherlands B.V." is Philips Hue

#

(and potentially also some WiZ stuff, not sure)

#

in the top devices list, the "LUMI lumi.sensor_magnet.aq2" is actually a zigbee Aqara Door and Window Sensor.

cold harbor
gentle tulip
#

iirc for the same reason that custom integrations are - mqtt is a way for anyone to add arbitrary user-defined devices :/

#

i wouldn't be surprised if they try to figure out a way to identify mqtt devices provided by certain known systems like zigbee2mqtt to include them in the future.

thorny sluice
#

Helps that we have a good relationship with the guy who does MQTT, too.

#

But as Paulus has said, this is really a barebones thing.

gentle tulip
#

(they don't even include all of the built-in integrations at the moment - some intentionally, some probably just because they weren't sure the data would be useful in the initial run)

cold harbor
#

I'm sure that the guys behind Zigbee2MQTT are prone to provide more accurate info about the devices, it's a nice piece of software 🙂

thorny sluice
cold harbor
#

And Z-wave devices are included? 🤔

thorny sluice
#

ESPHome devices tend to be way more DIY.

#

Z-Wave is an industry standard.

gentle tulip
#

I think zwave devices might be for folks using the zwave_js integration? I haven't spotted any in the device list tho.

cold harbor
gentle tulip
#

oh, yep, zwave_js is in the integrations list. there's some there.

proud parrot
#

you need to use the zwave_js integration regardless of how you run the actual server

cold harbor
gentle tulip
#

zigbee is included, but only via the zha integration

thorny sluice
#

Zigbee is.

#

MQTT is not.

cold harbor
#

Well...

proud parrot
#

Fortunately, Z2M provides a quite comprehensive database of Zigbee devices

thorny sluice
#

Just for reference.

gentle tulip
#

zha is a way to connect zigbee devices to home assistant. mqtt is a way to connect arbitrary externally managed devices from many different systems, anything from big open source server projects like zigbee2mqtt to someone running a shell script that updates the count of files in their trash folder :)

#

(although i'd probably use a webhook for the latter, it would probably be easier to set up)

cold harbor
#

Yes, but I'm afraid a lot of legitimate ZigBee devices connected via Zigbee2MQTT are not counting in the statistics

#

Let's wait for further versions/updates 😉

stoic briar
cold harbor
gentle tulip
cold harbor
#

Yes, I've read it, thanks anyway 🙂

gentle tulip
#

alright, then you already know the answer to that question :)

swift vine
stoic briar
swift vine
#

Yeah I know

cold harbor
#

I think there would be very interesting to have the maximum info as possible. Once with the info, you can filter or clean it. Not having devices that are widely adopted makes the whole image very partial. I don't get the point then. I think that dirty or not optimal info is better than partial info. Just my opinion, as a developer that works with huge amounts of data 🙂

onyx spire
#

maybe some kind of DIY advisory for ESPHome devices ? (as in : this board/chipset and this sensor was used.)
It would depend on creators providing that info, but it could be a way for them to help spread awareness and ideas which is a good thing as it may reduce the need to re-invent the wheel.

The tricky bit is that it will be hard to identify who should be credited with the design/concept unless you want to introduce a lot of duplicates into the system.
OTOH ... we will likely see a ton of duplicate devices anyway, because there are plenty of 'white label' products on Amazon et al that will be exposed for what they are with this database.

true tapir
#

Is their going to be beta access to the device database webpage

pearl swallow
fervent mural
onyx spire
# fervent mural The database focus is on devices that people can buy.

technically you can buy these esphome devices as well ... (the Everything Presence Lite being one example), but focussing on regular retail devices is probably best.
Plenty of problems to solve with those.
For example my Govee devices tend to identify themselves as either 'generic device' or some sort of Chinese manufacturer when using tools like Fing on my network.
It would be nice if the device database could include that kind of info as well.

fervent mural
#

Everything presence will be added to the DB, just manually.

#

People are too obsessed with the automatic uploads, what's included or not. It's only to bootstrap the system. Manual input will be possible

onyx spire
#

'obsessed' ? not really.
It's the less technical amongst us that want to help provide data to the system without polluting it.
I kind of like how sites like MusicBrainz do it where they show the data that you are uploading while allowing you to add/expand it as much as you are comfortable with.

#

and some of it is pure interest. Like ... what does my system really know about the devices I'm using ?
Why the heck is my Govee Light reporting as 'shenzen whatever' ?

#

It's a bit like discovering that the supposedly competing brands of soda are all owned by the same company.

cold harbor
#

Well, I think this is a start point, with a lot of room for improvement

valid otter
muted axle
valid otter
#

👋 I wanted to take this opportunity and thank everyone for opting in and contributing your anonymous device data!

We're steadily approaching the first 100k submissions with >60k devices stemming from nearly 20k HA instances.

But of course we're just getting started 😀

With rising amount of submissions we also see a broader device spectrum and of course also more duplicates - which was expected.

While we have basic deduplication in place we're taking the next steps to work on further reducing noise for submissions and existing data, while also thinking about how to visualize the database in terms of a web interface to interact with going forward.

If you want to engage on those topics further head over to the discussions and the project channel #1361754948949512203

Thanks again ❤️

magic acorn
valid otter
magic acorn
#

Currently the Grafana filters don't work. It would be a quick win, so we could play around a little with the stats as they are. Any idea when to fix this? 😅

valid otter
floral stream
#

Currently the Grafana filters don't work

swift vine
cold harbor
#

Maybe submissions with all Zigbee2MQTT devices? 🤷‍♂️

cold harbor
valid otter
# swift vine Wait.. So 30k+ submissions to the device database had no devices?

Not all devices are included based on their integration, like Z2M.

Generally, submissions are counted globally for all participating HA instances. And since submissions are done on a daily basis for each instance participating chances are likely that not that many new devices will pop-up compared to the amount of submissions.

#

So, yes @cold harbor

swift vine
#

Gotcha

#

Was just a surprising thing to read, was imagining a third of people being intentional unhelpful lol

cold harbor
#

As I said earlier, I would prefer a "cleanable" but real and raw data than a non existent data of a widespread integration and a lot of devices, but is only my opinion 🙂

floral stream
#

we are doing some data analysis at the moment and are planning to reach out to integration owners if we spot any obvious patters (we are about 1/4 of the way through 🙈)
we might end up publishing dumps of the raw data, but right now we are just really busy making sense of everything we've received

floral stream
prisma fjord
#

just curious about what way this data is licensed - can anybody do anything with it, like maybe https://smarthomeindex.com/ have their own database of smart home devices. I'm wondering would the ODBL that OpenStreetMap uses would be a good fit if one hasn't yet been chosen?

floral stream
#

we haven't picked a specific license yet, so suggestions are more than welcome!

prisma fjord
marble granite
gentle tulip
#

Something to consider is that the plain data about devices (device names, ids, supported open protocols, etc.) might not be copyrightable regardless of whether it's automatically collected or manually entered - depending on which specific laws apply. (This is why the main musicbrainz data dump is public domain!)

#

User contributions on the edit page definitely are copyrightable - stuff like descriptions, set up guides, etc. I would probably recommend a CC license for this part of the data.

gentle tulip
marble granite
valid otter
#

Hi everyone,

by definition we are currently collecting just a basic set of anonymous device data to start building the database.

Meanwhile, you already mentioned a couple of suggestions what to potentially include in addition ❤️

To have your thoughts and suggestions a little more structure I've created this discussion - feel free to chime in
https://github.com/orgs/OHF-Device-Database/discussions/123

valid otter
#

Hi @nimble elk 👋

Pretty sure that you're in the wrong channel for this question 🙂

This one here is about the OHF Device Database - a new initiative established to build the Wikipedia of smart home devices - Read more here https://www.home-assistant.io/blog/2026/02/02/about-device-database/

If you're asking whether we store history data for a device - we don't. What we currently store is defined in our Data Use Statement (https://www.openhomefoundation.org/device-database-data-use-statement/) and there is a discussion started what to potentially include going forward here https://github.com/orgs/OHF-Device-Database/discussions/123

nimble elk
#

Sorry, my question has nothing to do with this database

valid otter
clever thorn
#

Looks like our Mitsubishi Electric (in the comfort app) heating/air conditioning units aren’t in HA. Is there a work around?

proud parrot
#

The database is just from the set of users that have added devices and chose to report their data

gentle tulip
#

once the actual database ui is built, it hopefully will help direct people as to whether and how a given device can be integrated with ha :)

valid otter
sullen flare
proud parrot
#

Perhaps for the OP. I just googled for a device I have no experience with 🙂

gusty plinth
#

Hey everyone 👋
Has anyone here had good real-world experience with the THIRDREALITY Zigbee Smart Watering Kit for Potted Plants (Zigbee watering system)?
I’m mainly interested in how it behaves with Home Assistant / Zigbee2MQTT (or ZHA): pairing reliability, reporting/controls, battery life, and whether it’s been stable long-term.
Any feedback (or alternatives you’d recommend) would be really appreciated. 🙏

limpid tiger
lyric willow
#

Question for you guys, I have historically used Homeseer for my automation, but am looking to swap over to HA. Most of what I have done is Z-Wave and Homeseer uses the Z-Wave JS. Is there any way to simply move that over from HomeSeer to HA or am I going to have to go through and reset and readd all my devices to a new Z-Wave JS under HA?

#

Nevermind, found a thread on this topic from last year so it is recent enough

gilded doveBOT
unreal flame
#

Q: I'm sorry if this is in the docs, but I think a lot of people looking for full-spectrum device compatibility end up here. Is the Device Database an internal tool for optimizing compatibility or ultimately an end-user, searchable database of devices and how well they integrate/function? Just curious - I'm intersted in both - thank you!

valid otter
# unreal flame Q: I'm sorry if this is in the docs, but I think a lot of people looking for ful...

Hi @unreal flame 👋

The Device Database is an open, community-driven project aimed at giving everyone a public resource to make more informed decisions about smart home devices, or just to browse what's out there 🙂

So no, this isn't something we're keeping to ourselves. We're building it to be freely available for everyone to use.

We're currently working on a public web interface that will make all the device data submitted by participating Home Assistant users accessible to anyone. Of course, we also plan to leverage this data in other projects where it can add real value, like using it to guide users through device setup in Home Assistant, for example. And of course whatever else our community deems valuable to use the device database for.

We're still in the early stages, but launching a public, user-friendly web interface is our next major goal. Everyone's welcome to join us and help shape this journey!

unreal flame
#

Thank you for enumerating the intentions. I already opted in as I support either outcome, but a searchable database - however incomplete and occasionally erroneous - built by community data would be worlds better than the trial-and-error, internet-wisdom decisions currently being made without confidence. Thanks again.

modest crane
#

Oh wow, I just did a little browsing of the DB on the Grafana page. As we used to say in the big-data world, there's a ship-load of data cleansing required to make it useful for any sort of statistics-based conclusions. But I'm still very glad it's here; we've at least got some solid facts to look at. Thanks.

valid otter
# modest crane Oh wow, I just did a little browsing of the DB on the Grafana page. As we used t...

Yes, that's by nature I'd say 🙂
If you're more interested in the activities around that here's the discussion about the current efforts https://github.com/orgs/OHF-Device-Database/discussions/121

GitHub
Filtering out noise & improving deduplication to reduce device dupl...

As we have seen with white label brands like Tuya but also generally with how integrations are reporting devices regarding the fields manufacturer and model we want to focus more on reducing the &q...

valid otter
#

Hi everyone 👋

As we need to establish a basic set of device categories to get started, we'd love your thoughts and feedback to help shape our first iteration.

To keep the discussion open and accessible to everyone, we've started a thread here: https://github.com/orgs/OHF-Device-Database/discussions/137

The first post outlines our core categorization principles and links to a public Google Sheet with the current proposed categories.

Of course we're not aiming for perfection from the start. It's a sound starting point and we'll adjust as we go based on our learnings.

Would love to hear your input!

Thanks 👍

valid otter
#

Hi everyone 👋

valid otter
#

Hi everyone 👋

Since we're approaching our next 2-month roadmap cycle we wanted to share a short heads-up on the progress and next steps with you all.

If you've followed our public roadmap opportunity (https://github.com/OpenHomeFoundation/roadmap/issues/37) we've provided an update a couple of weeks ago that we're going to invest a little more time not only on the technical foundation but also to work on the first visual and interaction design for the website - something where we progressed slower than originally expected. So, for the remainder weeks of this cycle we aim to complete that opportunity to have a good foundation to continue.

For the next 2-month cycle we aim to launch the first version of device database website (https://github.com/OpenHomeFoundation/roadmap/issues/128) - most likely still without the final "branding" but something to work with, explore and jointly iterate upon.

Meanwhile, as usual we're happy to talk about your inputs and feedback in the open discussions (https://github.com/orgs/OHF-Device-Database/discussions/)

Thanks again!