Right now the actions "Store Audio Volumes" and "Restore Audio Volumes" always use the same set of global variables. So it is not possible to have several independent sets of volume variables for different flows nor is it possible to have "local" storage of that values only within a flow to save the values at flow start and restore them when the flow ends.
My suggestion would be to add a prefix for the variable name to these actions. The default would be "global_" to mimic the current behaviour.
If I enter "global_xyz_" a different set of variables like "global_xyz_volume_ring" etc. would be created.
If I omit "global_" the result would be local variables.
Post your feature requets for new triggers, conditions, actions and other improvements.
1 post • Page 1 of 1