Returns and bulk requests

[Hizo]

Hello,

after some time using the software, here are some feedback and requests in a random order, these are just feedback, no obligation or dissatisfaction on my part.

The work already done is great!

Scenes

• Allow modifying the icon of the scenes once created (we can rename them but not change the icon).
• Allow duplicating scenes to avoid recreating everything from scratch when making very similar scenes.
• Specify the material that triggered the scene when there are multiple possible triggers.
• Automatically retrieve the value of the material when it is active (it would save time and be more user-friendly).
• Add a button to insert an action (between two others already defined) so as not to redo everything if one was missed in the scene.
• Add a comment field.
  It would be great to create blocks with the title of your choice and put what you want in them without considering the location
  Allow modifying the value of another material?

Dashboard

• Allow creating blocks with custom titles.
• Allow mixing materials in blocks (e.g., I want to gather the status of windows in a single block).
• Allow simply enlarging the size of the blocks (it’s not nice when there are line breaks or horizontal scrollbars) (is it possible to modify the CSS files? If so, where are they?).

Others

• Allow exporting and reimporting configurations (even if more complicated than in the Plus version) because now I want to reformat my Raspberry and I will have to start all over again. So, if there is a way to save the configuration, I would be interested!

Thanks again for this great work!!

PS: I am on version 4.3.1, the update via Docker does not seem to work (at the same time I have done a lot of tests on various things…), hence my desire to switch to the ready-made Raspbian version (and it allows me to get rid of Ubuntu which is not very suitable for the transition).

[VonOx]

@Hizo

I am on version 4.3.1, the update via docker does not seem to work

Did you create the watchtower container? It’s the one that updates the containers (check the installation documentation)

[Hizo]

Yes yes, I created it by following the documentation.
But as I said, it’s an opportunity to start fresh.

The main disadvantage is having to connect all the elements when they are installed all over the house and not necessarily accessible.

Regarding the update issue,
What is strange is that in Settings > System > Operation Block, it says that Gladys is up to date in v4.3.1

After recreating the watcher command:

docker ps
4a1c17dd0bed | containrrr/watchtower | "/watchtower --clean…" | 6 seconds ago | Up 4 seconds  | 8080/tcp | watchtower

[pierre-gilles]

Hello @Hizo! Back from vacation, I’m responding to your message. Thanks for this super complete feedback!

@Hizo

Allow the modification of the icon of the scenes once created (we can rename them but not change the icon).

I agree, it’s a shortcoming!

@Hizo

Allow duplicating scenes so as not to recreate everything from scratch when we have very close scenes.

Yes too, I think there’s already a feature request for that, and I agree!

@Hizo

Specify the device that triggered the scene when there are multiple possible triggers.

What do you mean?

@Hizo

Automatically retrieve the value of the device when it is active (it would save time and be more user-friendly).

What do you mean?

@Hizo

Add a button to insert an action (between two others already defined) so as not to redo everything if you missed one in the scene.

Are you talking from an « aesthetic » point of view? Adding actions in the same action group does not change the order of execution, all actions in an action group are executed in parallel, so I see little interest

@Hizo

Add a comment field.
It would be possible to create blocks with the title of your choice and put what you want without taking into account the location

Why not! Can you create a feature request for that?

@Hizo

Allow modifying the value of another device?

I think you are talking about this:

Contrôle des périphériques multilevel dans les scènes

Cette fonctionnalité étant assez crucial effectivement, et assez simple à développer, j’ai avancé son développement malgré le fait qu’elle ait peu de votes J’ai travaillé dessus hier après-midi et ce matin: Contrôle d’un périphérique multilevel [Screenshot 2021-07-15 at 11.20.39] Contrôle d’un périphérique couleur [Screenshot 2021-07-15 at 11.20.58] Contrôle d’une température de lampe [Screenshot 2021-07-15 at 11.31.36] Contrôle d’un périphérique binaire [Screenshot 2021-07…

I developed it this summer, and it’s going in the next release

@Hizo

Allow creating blocks with custom titles.

On which dashboard box would you see this for example?

Each box has a meaningful title (device in the room = the name of the room), and when it makes sense (ex: the camera box), you can already customize the title.

@Hizo

Allow mixing devices in blocks (ex: I want to gather the status of the windows in a single block).

Are you talking about a « device » box across rooms? That’s not stupid Can you make a feature request for that?

@Hizo

Allow simply enlarging the size of the blocks (not nice when there are line breaks or horizontal scroll bars) (is it possible to modify the css files? If yes, where are they?).

I think we just need to remove the limit, I put them because at the time we couldn’t select the devices we wanted to display I think (it displayed everything)

I’m just going to remove the limit.

We already have a github issue for that:

https://github.com/GladysAssistant/Gladys/issues/1206

@Hizo

• Allow exporting and reimporting configs (even if more complicated than in version plus) because I want to reformat my raspberry and I will have to start all over again. So if there is a way to save the config I am interested!

You go to the folder where you saved your configuration (look at the Docker volume you put)

By default on the site we put everything in « /var/lib/gladysassistant »

In this folder there is an SQLite folder: it’s Gladys’s DB that contains all your configuration, you can set it aside

The only thing that won’t be kept is the additional containers like Zigbee2mqtt, we don’t have a process to restart from the DB and rebuild these containers, but it would be worth it to be able to manage that

@Hizo

PS: I am on version 4.3.1, the update via docker does not seem to work

If you took the watchtower command on the site, we force the update every 24 hours (it’s intentional, so that not everyone updates at the same time, it makes releases that spread over 24 hours. We made this choice also because Docker has limits on their unauthenticated API)

Thanks again for your feedback!

[VonOx]

@pierre-gilles

@Hizo

Allow mixing materials in blocks (e.g., I want to gather the status of windows in a single block).

Are you talking about a cross-room « device » box? That’s not a bad idea Can you make a feature request for that?

I will create the request because with the multidashboard it makes even more sense

[VonOx]

I created the request

Ajout d'une box devices qui ne soit pas dépendante de la pièce ( cross room )

Le titre parle de lui même, le besoin est d’avoir une box qui permette d’afficher les features des devices indépendamment de la pièce. Exemple on pourrait regrouper toutes les devices features batterie pour avoir d’un seul coup d’oeil le niveau de batterie de nos périphériques. Je penses aussi à @Terdious , la box pourrai avoir un filtre optionnel sur le type de feature ( température / batterie etc … ) car avec une grosse installation la liste va probablement être longue comme le bras. Le bu…

Now we vote

[Hizo]

Hello,

thank you for these answers.

@Hizo

Specify the equipment that triggered the scene when there are multiple possible triggers.

In the idea:

• Either we create 2 identical scenes by simply modifying the trigger.
• Or we create 1 scene with 2 possible triggers. And in this case, it would be good to know which trigger was activated.

@Hizo

Automatically retrieve the value of the equipment when it is active (it would save time and be more user-friendly).

When the trigger is a state change, by default, its value should be retrieved to avoid having the user do this action.

@pierre-gilles

Are you talking from an « aesthetic » point of view? Adding actions in the same action group does not change the order of execution, all actions in an action group are executed in parallel, so I see little interest

No no, imagine, I created my entire scene (so several actions one after the other) and I realize that I forgot a step, like waiting 1 min before the rest.
Do I have to start all over from scratch or can I insert this action before a block?

@Hizo

Add a comment field.

@pierre-gilles

I developed it this summer, and it’s coming in the next release

Awesome, that’s exactly it

@pierre-gilles

I think we just need to remove the limit, I put them because at the time we couldn’t select the devices we wanted to display I think (it displayed everything)

I’ll just remove the limit.

Thanks

@pierre-gilles

You go to the folder where you saved your configuration (look at the Docker volume you set)

By default on the site we put everything in « /var/lib/gladysassistant »

In this folder there is a SQLite folder: it’s the Gladys DB that contains all your configuration, you can set it aside

The only thing that won’t be kept is the additional containers like Zigbee2mqtt, we don’t have a process to restart from the DB and rebuild these containers, but it would be worth it to be able to manage that

When you say that additional containers like Zigbee2mqtt are not taken back, does that mean you just have to install the docker before or does that mean you have to unmount the Zigbee hardware to reconnect with Zigbee2mqtt?

@VonOx

I will create the request because with the multidashbord it makes even more sense

Thanks, I voted!!

Once again, thank you for all this work!

[pierre-gilles]

@Hizo

• And in this case, it would be good to know what the trigger that was activated is.

You mean how to know it? In a scene action (like « send a message »), do you want to be able to retrieve the device that triggered the scene?

Explain your use case

@Hizo

When the trigger is a state change, by default, its value should be retrieved to avoid making the user do this action.

I see, to give you an idea behind this feature, the original idea was to be able to fetch a value, then wait 10 minutes (for example), then fetch another value (from the same sensor), and thus you can use the 2 values from the same sensor (I don’t know if that’s clear)

But indeed I already got the feedback, maybe we could just fetch all values by default…

@Hizo

No no, imagine, I created my entire scene (so several actions one after the other) and I realize that I forgot a step, like waiting 1 minute before the rest.
Am I forced to start all over again or can I insert this action before a block?

Ok I see the idea!

I created a feature request:

Ajouter un groupe d'action au milieu d'une scène

Actuellement, il n’est pas possible d’insérer un groupe d’action au milieu d’une scène Cf demandé ici:

@Hizo

Add a comment field.

Feature request created:

Ajouter une description aux scènes

Pouvoir mettre une description aux scènes [Gladys04] Cf demandée ici:

@Hizo

When you say that additional containers like Zigbee2mqtt are not included, does that mean you just need to install the docker before

You will just need to restart a Zigbee2mqtt container (in the gladys UI), but otherwise no all your devices will be there (they are in the DB)

@Hizo

Once again, thank you for all this work!

You’re welcome!

[Hizo]

@pierre-gilles

You’re talking about knowing how? In a scene action (like « send a message »), you want to be able to retrieve the device that triggered the scene?

That’s exactly it

@pierre-gilles

I see, to give you an idea behind this feature, the idea behind doing it this way is to be able to fetch a value, then wait 10 minutes (for example), then fetch another value (from the same sensor), and thus you can use the 2 values from the same sensor (I don’t know if it’s clear)

But indeed, I already had the feedback, maybe we could just fetch all the values by default…

Indeed, it’s not a bad way to work, but maybe we can do both
Retrieve the default value and if you want others, perform the action.

@pierre-gilles

I created a feature request:

Thanks, I voted

@Hizo

Add a comment field.

Thanks for creating the request and for the record it’s silly but very practical I find.
I voted.

@pierre-gilles

You will just need to restart a Zigbee2mqtt container (in the gladys UI), but otherwise no all your devices will be there (they are in the DB)

Super!
I will test all this when I have more time.
But it might be good to talk about it in the wiki

[pierre-gilles]

@Hizo

Indeed, this is not a bad way to work, but maybe we can do both
Retrieve the default value and if we want others, perform the action.

Request created:

La box "Continuer seulement si" devrait proposer les valeurs instantanée des appareils par défaut

En plus de laisser la possibilité de comparer des variables créé précédemment, laisser la possibilité de prendre une valeur instantanée sans devoir à créer une action « get device value » Demandée ici:

[Terdious]

@Hizo

Allow modification of the icon of scenes once created (you can rename them but not change the icon).

Feature request created (it wasn’t before ^^) :

Modification de l’icône des scènes après création

Feature description Suite demande de @spenceur et de @Hizo : Permettre la modification de l’icône des scènes une fois créées (on peut les renommer mais pas changer l’icône). Fait référence à : et à :