The problem is we always run into “my use case is not your use case.” I have not had success in the past with device taxonomies that divide based on expected use case.
Contact sensors are good example. If I use them on the kitchen drawer, which I do, then they’re going to get separated From discussions of exactly the same sensor used on the door and separated again from exactly the same sensor used outdoors on the gate. And maybe separated a fourth time from the exact same sensor used on a chicken coop, which someone puts under “animals.”
I’m not sure what “people, places, transport,” means in terms of devices. Or where in the suggested taxonomy would conversations about the jawbone up fitness band or the Apple Watch or Amazon Echo go.
I think it’s fine if you want to have broader categories, anything would be better than what we have now. But I would avoid making use case assumptions. So maybe something as simple as:
Heating and Cooling
Would pull out the biggest repetitive topics and leave everything else tumbled together.
After all, we don’t get that many topics about power generation, aquariums, or fitness bands. We get some, but it’s fairly easy to find the relevant threads.
The ones where you have to search through dozens of similar topics are in the big four areas: lighting, sensors, locks, and HVAC.
I listed window coverings As its own category just because The information in the threads tends to stay good for a pretty long time, but people usually have no idea what the brands are when they first start looking. So new people don’t recognize that threads are relevant just from the topic titles. But it could be shoved over to other as well, there aren’t that many threads on the topic.
So just speaking for myself, I do prefer having very granular narrow categories when it comes to device discussions. But again, anything is better than what we have now. If we go for broader categories then I flip to the other side and I like to see just four or five big categories based on device class.