Help with [APP] Flow Event Bus

I need help with understanding Flow Event Bus App for Homey | Homey .
I may be slow, but bear with me.

I’ve seen the description, plus a few forum posts where it has been explained as a good app for “stupid” buttons, but no concrete examples, and here I am, unable to see the advantage of using it vs regular start flow and the logic/variables.

If someone would be kind to help me with an example - a simple flow with an explanation would suffice. Or you can use one of the two below to explain how to implement the app. Thank you!

I have a RF remote with 8 buttons.

Homey can detect them being pressed (Telldus App for Homey | Homey). I want to split them into 6 functions-, and 2 program buttons, and use them as follows:
a) to do a specific thing when one of 6 function buttons is being pressed
b) to have 6 function buttons do some other funtions if one of the 2 program buttons is pressed first.
I.e. to have 18 different funtions with 6+2 buttons
Does that make sense?

Another example would be a button which toggles through some light scenes by using iteration of variables (i+1) and the regular “this flow is started” with corresponding AND criteria and many flows.

Now, are those two examples something to do with Flow event bus? I am able to do that with timers and variables, but would love to make it more elegant and efficient. How to do that with this app?

If this isn’t a good place to use it, what is? Do you have an example (preferably with a brief explanation to it :slight_smile: ) I see people in forum are excited to use the app and I want in on the ride.

Bump. :slight_smile:
Anyone willing to share a flow as an example of the use of the app?

From made some flows using the example on the app’ app store page.

(Kanaal = Channel
Knop = Button / knob)

I hope it makes some more sense

1 Like

Lovely Peter, it does make sense, thank you.

But what is the benefit of using this VS


Beacuse, people obviously are seeing something that I am missing? :smiley:


OK, I get it, it’s a way of categorizing your flows to use this app instead of having a bunch of This Flow is started triggers


Yes the “this flow is started” card is fun, but not practical if the flow n# grows to 600

Here’s a neat tool if you want to simply generate an overview list of flows with those triggers (and muuuuch more!): Flow Checker

1 Like

Yeah, I use Flow Checker as well :slight_smile:
You can see if there is a flow with This Flow… trigger, but not once it’s referred to from some other flow, right?
Anyway, that’s how I found the Flow Event Bus app - by searching for other flow utility apps.

I’ve also seen many threads where the latter was mentioned end up with someone suggesting using the HOOP app. I’ve seen what it can do, but haven’t got the time to check what happens with back up, warranty and such when using community apps, so didn’t realy invest myself in it. If it’s as fast as regular flows, I think I’ll end up there myself as well, mostly because of multiple triggers and elseifs in AND. That reminds me of something for a new thread.

Thanks again, Peter! :smiley:

1 Like

That could have been me :sweat_smile:

No, it just lists all flows starting with ‘This flow is started’.

I have no idea where or how you can find which flow(s) trigger a certain flow with ‘This flow is started’.
Besides use logcards on every flow action and compare the logs.

You brought me to ideas here, I didn’t use Event Bus yet, but I’m going to now.
One disadvantage You have an app in between the trigger flow(s) and triggered flow. Apps can stop or crash.
BUT, no big deal while FlowChecker notifies you for that, while a bunch of flows break if an app quits.

An alternative way for Event Bus:
If you trust the Timeline, you can misuse it while there’s a triggercard “A notification was sent”
(Timeline can be disabled without notice when it gets “rate limited”)

Okay, many topics here. Just to touch on some of your remarks, without hijacking the thread completely. :smiley:

I name flows in a certain way so that I have a group of them together, with sequential numbering (it looks like you have a similar system as well). That way I always know which flow comes after the other.
(1-1, 1-2, 1-3 and so on; where all flows starting from 1-2 have WHEN This Flow is started, that is triggered by the preceding flows (1-1), and so on. If this makes sense. :D)

This brings me to:

It looks like to me that the Flow Checker doesn’t show flows with This Flow is started (i.e. 1-2, 1-3…) if they are being called from some other flows, which they usually are in my flows. (I checked this now, just to be sure, and I don’t know if this is a bug or by design, given that it says UNUSED FLOWS OR FLOWS WITH A THIS FLOW HAS STARTED’ TRIGGER in the app. I have many flows that do start with This Flow…, but are not on the list. And, no they are not filtered shrug)


No Sunset to warm flow in the list, because it gets triggered from another flow.

But yeah, for me, this is a way to go. I used to have many push notifications on my previous Homey, and on this one I am kind of building the architecture first, and then I’ll see what needs (deserves) to get pushed :slight_smile:

What we need is Athom to put the possibility to track “interconnected” flows, and variables, the same way that they’ve started with devices and their respective flows here:

But, maybe now you see why I kind of need to start using the HOOP :smiley:

Ps. Yeah, I’ve seen that you are a HOOP evangelist in the threads :smiley: and scince I cannot code js, I have potential of become one, as well.

I didn’t realize, but it looks like it!
After some digging:
I found out, I have f.i. a set of 8 flows with the “ThisFlowIsStarted” trigger, and only one of them was listed.
After selecting that flow again, from the ‘master’ flow “Start a flow” card, it disappeared from the list.
There was a glitch obviously.

So, somewhere there IS a link or “interconnection” between those flows.
How convenient it would be if the flows which call the “TFIS” flows could be listed somewhere somehow.

Well, to locate the variables, u can use this script I posted here in the meantime:

Output example:

1 Like

W O W! This one is cool. I’ve seen it in the thread, but thought somehow you rewrote the FlowChecker for your personal use (what do I know?), didn’t realize it was a HomeyScript.

I’ll run it when I get on my desk top PC. :smiley:




It works! And it’s so great tool! Thank you very much for sharing it!
I especially like having both direct and indirect refs. Great job

1 Like

You’re welcome.
I’m not a script guy, I can read and edit them to some degree.
For this script and the other flow check scripts credits go to @RonnyW !
And Martijn Poppen based his Flow Checker app on those.


Then, the thanks goes out to them as well! :slight_smile:
I’ve noticed one, strange thing, though.

And I can’t really help with solving it in any way. But the daylight_check variable from the picture above is probably one of the most used variables in my flows, and it doesn’t show there for some reason…

For instance, there is no: Kitchen: Light ON 1 flow in the list.
So, I guess, be cautious when depending on the script when changing variables, because there might be some more flows using them.

That’s odd.
This is a var I use in the biggest number of flows, and all of them are listed…