Feature description
Hello 
When you start to have a fairly extensive installation with Gladys, you also start to have a lot of scenes!
I think it would be more readable and easier to use if we could put our scenes into categories (visible as a banner, for example) that can be hidden and displayed.
Or in the manner of Dashboards with a dropdown list?
Thank you
What I think is complicated is knowing whether we want predefined categories… or the ability to create our own categories. Since each user will want to create a scene that is unique to them, the same will go for the categories.
I also think we need to find a way to organize the scenes to manage them better.
I had considered the possibility of displaying them as a list whose order can be changed by drag & drop.
This would allow more to be displayed on a single page, with better readability.
Especially since by naming them appropriately, you can find your way around quite easily:
[LIGHTS] Dim the brightness in the evening
[ALERT] Mailbox mail
[ALERT] Temperature < 15°
[INFO] The dog's bowl is empty
Etc…
Yes, for me I was already thinking about categories created by users as we do for the Dashboards.
I think the goal would be to be able to have a possible separation between the scenes of your choice.
For example, in my case, I could separate the scenes of my aquarium, the living room lighting, and the scenes of the alarm system.
Why not, I can see a filterable tag system for example! Something to think about 
@Checconio Since you say your installation is becoming quite extensive, would you be interested in being interviewed for my YouTube series « Gladys Assistant chez vous »?
(https://www.youtube.com/playlist?list=PLkBwN_hZI5TeMkv-sZ0UdU4AVxIOHefIG)
(We can discuss this privately if you like, to avoid cluttering the topic here)
That’s a great idea 
especially since it’s usually very simple for the user to use, and it’s very flexible: a scene can have multiple tags.
Yes a tag will allow displaying the same scene in multiple « views » which is indeed better than what I had in mind
Small bump because this point is starting to interest me 
I’ve got a parent scene that is triggered by a motion sensor.
This scene only triggers scenes in // which themselves trigger others ^^
So I end up with a lot of scenes and it’s quickly confusing
)
You’re right, I just used a lib « react-tag-input-component »
Ok I don’t see anything similar as a lib on the internet. I’ll probably create my own component. Should I try to make it as generic as possible so we can use it elsewhere?
Yes, now that you say it it’s obvious.
I think I’ll have to make changes in the models for that because for the moment I had gone with an array of strings in the devices. But to have access to all the tags of all the scenes I think I’ll have to create a « tags » table and a « device_tag » table. And therefore add new CRUD routes to manage the tags, what do you think?
Again, I think adding a « tags » table is important because that will avoid having to go through all the scenes to get all the tags.
Wouldn’t it be better to abandon the table view of scenes for just a list? Because we’re adding more and more things to the scenes display and we have less and less space.
That’s better, yes
I imagine you mean « scenes » and not device
Indeed I prefer a relational approach, we’re rather relational on the project
I see 2 options:
t_tag_scene:
- scene_id uuid
- name text
To find all available tags, simply do:
SELECT DISTINCT name FROM t_tag_scene
The option with the relation table is good if we ever wanted to really add additional options to the tags, but in our case here it might be overkill
I’d lean more towards option 2 personally, what do you think?
I don’t think so, we just need to rethink the display inside the card
@pierre-gilles :
I’m making a small suggestion using the « react-select » lib that we already use in gladys.
Your solution is not bad, but it looks « odd » within the rest of the editing interface.
Just my two cents, personally I like it this way it’s not intrusive, it’s easy to use, it gets the job done, I think
The relational table is surely a good idea; reading that I thought it could be useful to be able to work on the devices!! I’m thinking specifically of MQTT devices that are also used virtually. Being able to link virtual devices to physical devices via tags, for example group the virtual ones, etc!!
Not a fan either, functional but it looks a bit like a « big block » in the middle of the screen, it doesn’t really fit into the existing design
If you don’t have many ideas, what I usually do is see how other products handle it: open a few products you use that have this kind of tagging system, and see how they do it. There’s no point reinventing the wheel when designers from big companies have already worked on this for hours 
For example, GitHub has split their « issue » page into 2 parts:
With the editing on the right (tags, etc..)
If you look at Zapier (which does the same thing as us: scenes), they have the same behavior as GitHub, a bar on the right:
If you click on « Settings », it looks like this:
I’m not saying it’s the solution, but in my opinion it’s worth exploring! It would allow you to put your component « react-select » in a sidebar that would be « delimited » and wouldn’t take 100% of the width.
I have quite a few projects in mind for the scenes: viewing the execution history of the scenes, with what happened in each run, and that could fit in this sidebar
What do you think?
One thing at a time, let’s stay focused here.
Very promising!
This morning I was thinking that we could add filters to the scenes view.
For example: active / disabled / by type of triggers (selection of devices) / etc.
