If I tag a device as an ‘appliance’, I expect that if i’m filtering on sensor entities related to aplliances, I would be able to do it. However this doesn’t seem to be the case. entities have no idea there is a label on the device.
On the contrary it also doesn’t make sense to tag all the entities under the same device manually.
I think there should be a split between entity labels and device labels through the whole system.
If i’m setting an automation for example, I should be able to select by device label or by entity label or both. Same should apply in filters etc if they are to be kept separately. Otherwise, entities should by default always inherit also the device labels.
First WTH is a special event only happens every few years may want to consider a title change.
I 100 % DO NOT want inheritance like this and need them to remain independent. Having the device and ents associated index separate allows FOR VERY rich context application to the device cluster.
(I’ve built an indexer for labels for Fridays zen and this would break the hell out of the schema I very much rely on this not being true)
Hence why I suggested to keep them separate now at this stage. but have the avility to look at the device tags if needed in various parts of the system
That’s exactly what my indexer does. Gon read it. But they should ALWAYS stay separate but part of the same schema and works exactly how you want it to work. They should be in the same store but NEVER inherit. If you want an inheritance query the parent.