Hello,
I have a large number of scenes that often contain multiple sensors/actuators, and some scenes in which those same sensors/actuators appear. I would like to know whether it would be possible to have a list of the scenes in which a given sensor/actuator appears, using a search box?
Thanks,
Jean
Hello @je
1 Like
Indeed, that would be very convenient; to make up for this shortcoming, I name them in the tags.
4 Likes
I agree with the need. I had described it in this thread :
I suggest casting your votes on my thread, and maybe commenting 
Because I hadn’t convinced @pierre-gilles… If more of us specify the need, maybe that could…
2 Likes
Tags are indeed the best way to organize scenes 
For my part, I have one tag per room + tags for certain « functions » (Alarm, Voice, Air conditioning).
When it’s well organized, it’s very easy to find
Hello
that’s the problem, , but when you have several devices, you have to tag them all and that makes a lot of tags 
I agree with @Psoy, and I’ll clarify my point of view: tags are perfect for organizing things you need to find fairly often, or for logically marking the major ‹ categories › of scenes. But it’s not feasible to tag absolutely everything for a hypothetical use.
And to illustrate this, here’s the typical use case for this feature request: I have about a hundred zigbee or mqtt devices, and I’m about to remove one of them. And since I hadn’t planned that, I don’t have a specific tag in my scenes, and I no longer remember for sure if any of them uses this device. Filtering the scenes that use this device would really be the most effective
@pierre-gilles is it a technical issue that’s making you hesitate?
1 Like
I agree with all the points raised; this development is essential. In my case I even abandoned some groupings of scenes and automations for now because I couldn’t find my way around them. Too long. In the meantime I’ll look into it again using database queries, but as a result, it’s no longer user-friendly !!^^
No technical issue, the technical side is rarely the limiting factor
It’s more a design question: I like to preserve the product’s current simplicity, and you always have to find the right balance so as not to overload the interface.
If it’s only a matter of deletion for example, we could imagine another approach: when deleting a device, show a screen indicating:
« Warning, this device is used in the following scenes: [link to scene 1], [link to scene 2], etc. »
Thanks for your feedback, and glad to know that technical feasibility isn’t an issue
Your suggestion for deletion is a good idea, for sure. But I had described that use case because it seemed clear to me, though it’s not the only one.
Being able to filter scenes that use a device would, for example, also be very useful to check a device’s ‹ lifecycle ›. If I’m working on a scene or a dashboard that uses a device and I want to find all the scenes that can modify or use that same device, filtering scenes by device would be really effective.
I of course share your concern that Gladys should remain efficient and focused in its design, with tools placed in the right spot and having a clearly identified purpose. But I also believe that sometimes a slightly broader feature, without an extremely specific goal but with significant potential to be used in multiple situations, will improve the user experience
5 Likes