Right now I have home full with a lot of devices, and triggers that fire multiple times a day. Often one or two devices fail silently. I’d love to be able to add to the flow a tool to send the event twice (or more) but currently if you do it doesn’t go through. Even if you wire the event to directly, and through a delay, the delay won’t actually fire downstream, it stops where the non delayed event was seen. The only way around is setting up two triggers (like event, event + 30 seconds), but that is non obvious, makes the whole flow more cluttered, and doesn’t work for triggers that aren’t time based. I don’t mind writing an App to do it, I tried, but the rule of only emitting one event prohibits it from working.
Are you in Advanced or standard flows?
Are you events WHEN or THEN cards?
In advanced flows. For THEN cards. I don’t know how I’d even attempt to write something like this for standard flows unless an AND card can emit multiple downstream events (which would also be cool).
The plugin I tried to write was a then card.
I don’t know how to think about this with a WHEN card since I’m not creating the original trigger.
When a device sends a message to Homey the corresponding WHEN card should trigger. If not there is bug in the corresponding app. There is no way to solve that in a flow.
How ever a device could sent the message twice, to make sure the message get to Homey. But then the flow might trigger twice.
So I don’t understand your solution 
you can have two WHEN cards connecting to the same flow, so it will be starter by one of the two (different) WHEN cards. I have no clue what happen when you use two identical WHEN cards. I think the flow will run twice.
An AND card can connect to two THEN cards, but is the kind of event you have in mind?
Maybe post your flow or drawing.
I’m trying to achieve either creating a tool like the top flow that sends to events to the Set Position card x seconds apart or simply using the Delay tool to send the same event to the rest of the workflow twice. Both are impossible today. The only thing that you can do is something like this:
But this gets unwieldy very quickly with large flow.
And yes in this particular case I could create two triggers one with offset 0, one with offset 10, but for any device that doesn’t have the ability to trigger an event and then one 10 seconds later, it won’t work which means you simply can’t do that in the majority of flows.
Aren’t you trying to get a workaround as a tool to handle flaky functionality of devices / apps?
Imho it’s better to fix the main issues first.
I’ve never needed something you’d like as feature request.
I’m trying to work around that I have some events that trigger over 50 devices. It is quite common for one device to fail (sometimes two). I’m trying to come up with a way to deal with this issue without making my flows even bigger than some of them are. Given that they almost always work on a second attempt (unless Homey has lost connectivity to the device which requires a Homey restart to fix), I think firing a second event makes perfect sense. Are things flaky? Yes they can be. But with 179 devices currently connected, having one fail isn’t surprising. Especially over Matter (or anything else operating at the 2.4 GHz). Do I wish I hadn’t gone all in on Matter, yes. But I have and I’m trying to make things work reliably. Firing a second event does that. And trust me, I’d be happy if every device I have responded to every event every time. I’m just not that lucky,
If you put the two actions(not events 
) in one flow on one canvas, you can start that from the main flow.
Maybe use the error flow for this? Since you’ll only need the route when it’s not working as expected and assuming it results in an error at that moment. In this post i’ve posted an example flow.
So the error flow seems to be triggered when Homey can’t talk to the device, but the silent failures aren’t triggering the error flow. I find the error flows exceptionally useful when an actual error occurs.
I’ll have to figure out this one. I’m not sure I’ve given that a try yet but it is not something I’ve ever put together (a canvas being triggered from a flow).
Well, the naming convention of Homey is not clear: on a a canvas you can draw more then one flow. The canvas can be saved, and then you give it a name. When there is a start button on the canvas, you can call the canvas/flow from another flow.
So Athom calls a canvas also a flow.
To be precise:
- A canvas can only contain one start button. If you put multiple flows on a canvas, then only one of them can have a start button.
- When excuting a flow from another flow and provide the name of the canvas, you are actually refering to only the one specific flow on that canvas that contains the start button. The other flows on the canvas are not manually startable.
- If you want to be able to start all flows on a canvas manually, then you would need to connect the single start button to all flows on the canvas. This will always execute all the flows on the canvas at the same time. If you want to be able to execute those flows seperately, then you need to place each of them on a separate canvas.
1 Like
