Hi @pierre-gilles , so since I hadn’t understood anything about this topic (see my posts above), I’m happy to take the lead
I’ll take care this weekend of completing the table with what you’ve already exported and I’ll remove what I added since it’s 1:1 and not an improvement for now.
Hi @pierre-gilles,
I’ll see what sentence I can find to put for the cube but I must admit I’m a bit puzzled about what to put… And can we « remove » things from that list like the cube for example because apart from saying that this type represents the mode of a cube… personally I wouldn’t understand (and I already don’t understand )
It’s always the same with me, I have trouble seeing only the pure specific
And as I filled out the table, you can put all those commands for a television, but also for a VCR (watch out, Old School mode activated), an internet box, a Blu-Ray player, an A/V receiver, etc.
And all those commands are common so I tried « Device », but that might not be the right name and we can revert to « Television ».
Well, a bit like the previous point but for sound. You can have music but also a podcast, a radio, an audiobook, etc.
At first I went with « Mathematics » because it was for Surface, Volume, etc.
And then I thought we’d end up with a big bunch of categories, which I don’t find great right now.
So « Generic » is the closest, the name isn’t necessarily the best.
Yes, I think we can merge.
For Audio and Device, I don’t know if you prefer that we compact them or make more detailed categories: Television, Internet box, A/V receiver, DVD player, etc.
My idea is still to rationalize but I don’t know what that implies in the programming part later if there is grouping.
I feel like you’re falling into a classic development trap: wanting to generalize too much.
If we follow your reasoning, @mutmut, we risk ending up with a category « Object » or « Thing » that would encompass everything and anything (I’m exaggerating)
The goal is for the user to clearly understand what each category corresponds to.
Yes, the physical device may be an internet box or a Blu-Ray player, but in the end, the use remains the same: watching television.
Whether I watch TV via an Apple TV, a Bouygues box, or the TNT, it’s still… television!
Hard to find a clearer category than « Television » to describe this usage
The point isn’t to have a perfect, absolute classification, but simply an intuitive and clear organization for the user
From a programming point of view, we can do whatever we want, there are no limits
Hi @pierre-gilles
I’ve just done another pass on the terms, I think it’s fine.
I left a column with the old section names; you’ll need to delete it if everything looks good to you.
Some descriptions need to be validated and as soon as that’s done we can remove the orange/red color.
I tested creating features in mqtt to see examples, and for Image, you need a min and a max to save… for an image there I didn’t understand but I’m still not sure I understand how some features work
I have a small remark about line 190 for the « bed activity » of the vibration sensor.
I see that you restored the original description but I didn’t understand at all what a bed has to do with it and DeepL returned this to me:
Existing list of features
A clear name
)
(I’m exaggerating)
It’s really great!