Goodmorning,
only a suggestion.
I have many advanced flow to update value in different v-device from different sensor, question is ease:
i need to have many advanced workflow in which i update associated v-device or i can have a single advanced workflow in which i have many update workflow? one for every sensor and source?
thanks
Marco
You can have multiple Advanced Flows in one so-called Advanced Flow canvas.
Hi @MarcoZ ,
you can have as many single flows in one Advanced Flow as you like - and you can make them interact between each other.
The only problem is that you will face much earlier than you think errors where you cannot easily analyse, where they come from.
So there are good reasons why to combine them, if they are related to the same problem, or the same (virtual or real) devices, but only as long as you clearly keep the overview, what happens when.
But you can also group flows (Advanced and Standard Flows) by naming convention or folders and subfolders.
The only problem is, if you have too many of them, you often will not find easily the appropriate file or folder.
So with a couple of devices and flows, you can do, what you want. The more they are the more important is a good structure. And the earlier you think about a good structure, the easier it is to be consistent.
Good luck.
Oh that is the official distinction?
Thank you Dirk, good to know. And when I have different Advanced Flows in one canvas and start to connect them with arrows, is there another name for that than pot of spaghetti?
When Advanced Flows were introduced, Athom used the term “canvas” to describe the platform on which Advanced Flows are created. But as far as I know, this is not an “official” term.
Advanced Flow is a leap forward in the way users automate their smart home. With the same powerful Flow-cards that have already automated over hundreds of thousands of smart homes, Advanced Flow brings those existing Flow cards to an infinite canvas, for infinitely more possibilities.
(Source)
It is all up to you whether to create spaghetti or not. 
If you want to connect different flows but not creating spaghetti you should look at eg. Advanced Trigger app.
With this you can call other flows from multiple flows, with multiple arguments; just like functions/methods.
Of course you can also use Flow cards under Then for this.
Hi @DirkG thanks
yes, exactly — I have several advanced workflows that all do the same thing, but they start from different sensors and update different virtual sensors. So the action is the same, but performed on different sensors.
To explain it better: I have a sensor that measures the electrical consumption of a line, for example the lower floor. On that lower-floor line, there is a washing machine and a dryer, each with its own consumption sensor.
The virtual sensor is updated with the consumption detected by the line sensor, from which I subtract the consumption of the washing machine and the dryer.
The sensors enabled for energy are therefore the virtual line sensor and the sensors for the washing machine and dryer. This way, I avoid counting the washing machine and dryer consumption twice, while the physical line sensor is not enabled for energy.
I follow the same approach in the kitchen with the sensors for the oven, dishwasher, and fridge.
Thanks,
Marco
Keep in mind that the number of flow cards that you can place on a canvas is limited from a performance perspective.
It seems to depend on the combination of certain apps, type of action and tags/variables used, but you’ll know that you have reached the limit when opening and saving flows is taking longer and longer, until you cannot open/save the flow anymore.
I personally ran into this limitation while creating a custom status widget using the Enhanced Device Widget app + actions performed by the Better Logic Library app + various actions by standard Logic cards + various tags and variables used. That combination caused issues in those flows (also if I recreated them from scratch). After splitting them up, they can be edited normally again.
If you start noticing such delays and you have a lot of flows/flowcards on your canvas, its time to split up the flow across multiple canvasses.
thanks @SunBeech
i will keep in mind you suggestion!
