It asks me to fill in Return ID, then it executes as planned.
So now it suddenly works?
I copied the ‘switch’ and it sends a Yes or a No, dependent on the number of Y and N.
So I would say the Advanced Triggercards you use should be set to Yes and No as well…
The logic works. It’s basically “!A AND (!B OR !C)” for true and “A OR (B AND C)”. It’ll get a lot worse when I get the rest of the sensors up 
If I run this from “SensorLogic started…” it works just fine, but if I run from “Start SensorLogic…” it doesn’t call the upper part. If that made any sense at all.
My intention was to separate all the shared functionality and then call it from my flow. That way I can get rid of some complicated stuff, and I only have to maintain it once. The upper part is my “function”. The lower part is to trigger the function.
@Peter , @Anders_Gregow and @Arie_J_Godschalk : Thanks for the help. For some strange reason, reinstalling the app (without removing it) seems to have fixed it. Didn’t do any change to my logic, so…I’m stumped. It’s either working like it’s supposed to, or I’m so sleep deprived that I’m imagining it 
3 Likes
Hi @Peter_Kawa
I am missing something about passing back information via the Return card. When that is done, how do I access that return information in the flow that launched the triggered flow? Lets say I have a
card, and I return some info in the number 1 slot like this:
How do I use that return info. Like this?
Thanks in advance for any help you can give me!
Yeah, that should work yeah!
1 Like
And…
… it does!
(now at least 
)
I can finally easily pause my TTS speech casts for the actual duration of the sentence, yaaaay!
1 Like
Hmmm, does that mean I can use triggered flows recursively (ending the recursion using a stop condition, often based on returned results) - does it? Can I “nest” multiple self-executions?
Yeah i think so, but make sure it is not executed 60 times, else you will have the same flow running actively 60 times and homey will kill it and disable the flow.
1 Like
…Okay, tested it and I find it very interesting.
It looks like the last triggered flow at the bottom executed, including its tail that comes back up a depth, but it is not actually returning to the place of the then card in the parent flow, at least, the tail of that (with the next resurface, and the return to the grandparent) does not seem to be triggered, at least I am getting no log messages beyond the first return.
Maybe those flows all have the same ID, and the return closes all of them. Or maybe the return just doesn’t know how to jump back to a triggered advanced flow - even if it is the one that launched it. I don’t know.
Also, performance really, really bogs down when I run this - or at least, the flows either do not run at speed or they do not run consecutively. Those last two digits in the timestamps are minutes.
I don’t think I tripped any unintentional endless recursion, I don’t think. It could be some performance issue that stops the flow from returning, but it happened the same way at depth 6.
Anyone have any idea what is going on here? Why not return, and why the slow-down?
Here is a copy of the latest flow I used.
I’m still really interested in this. Anyone?
You dont have anything filled in the return values card.
No idea about the slowdown, the cards are made to be triggered very fast.
Hmmmm that return thing I can fix. But I’ll test when I have some free time, not now, unfortunately. Thank you for coming back to me!
1 Like
I really enjoy the Advanced Triggers, thank you to @Arie_J_Godschalk
Here’s something (link) I tried to solve with BLL but the easiest way, given the requirement to not use local variables and avoid many cards, was with Advanced Triggers.
Solution:
Still a lot of cards, but relatively easy to maintain. Tips welcome.
1 Like
Here:
First i create a BLL variable with an empty string in it.
Then i run a loop.
Then i write the variable to SSL.
Within the loop, well, you can see it yourself. Please note that after the true and false i have a linebreak (shift enter).
This is the shortest way i know. And weither you have 3, 10 or 50 items to check, you dont need anymore flowcards.
1 Like
Thanks Arie for all useful apps.
I have one (maybe stupid) question on Advanced Triggers.
The then-card (’Start..’) of 1x3, 3x3 and 5x3 publishes 10x3 tags on the output. I wonder what the purpose? Using only 3x3 then- & when-card, no overload and return-card.
No problem in function just getting a lot of tags after a chain of then-cards (each using the result of the previous).
Because those returncards could return 10x3 tags, and the amount of returning tags cannot be set dynamicly 
@Arie_J_Godschalk I am a big fan of Advanced Triggers, thanks so much.
I may be doing something it was not designed for, perhaps you can shed a light?
When working with iterations, they do not return values, except the last one:
Output
I wanted to export the flow with Device Capabilities, but it does not work atm.
