Returns and bulk requests

[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!