You can only start another simple flow that starts with a “when this flow is started” card, or a “when this flow is started with a (number/boolean/text/image)-tag” card. Or you can start another advanced flow that either has a start button, or at least one “when this flow is started with a (number/boolean/text/image)-tag” card, or a start button.
In both cases the flow will start from that point and will include the variable that you pass on as a tag that you can use in the flow.
If you want to start flow XX from another flow with “start flow…..’ flow XX has to have a ‘start’-button. Otherwise it isn’t listed in the possible choices.
Similar with the ‘start flow … with a tag’. Flow XX has to have a WHEN-card ‘ this flow was started with a tag’
Ah, Thank you for pointing that out. That is a little grey area I didn’t knew about. I tested it, but I would not recommend using it this way as it is very tricky. You could for instance use the “When Luminance is changed” card as a starting point, and it is trigger-able. But as soon as you actually use the Lumince value tag in your flow it isn’t trigger-able anymore.
I would just recommend to always start with either a “when this flow is started (with tag)” card, or a start button and connect those to a “and” card or a “then” card.
indeed, very shady business actually. It is very easy to break something in another flow without you actually realizing it. I’m surprised that Athom implemented it like this.