You too!
If it happens again let me know ! 
Had to un/reinstall. Did not correctly return the status of broken flows after I corrected them Doesn report anything anymore
@thobu theres a check interval. So itās not a instant fix when you fix tour flows. Only when the check runs for the next time it Will show them
Okay, letās see. As said. I donāt get anything atm
In that case all good 
Ehhhā¦where do I find those tags āFlowā and āflowIDā I see in your Flow example?

@Eternity when you use one of the flowchecker cards. The tags are connected to that. So they Will only be available in that flow
Thanks for solving that small mystery 
I know this question has been asked before, but I didnāt see (or overlooked) a follow-up:
@martijnpoppen is there a way to exclude a folder from checking? Or is this perhaps a good idea to implement in a future release?
Now, after Christmas, there are a lot of flows which I donāt use the whole year until next Christmas. But these flows are broken too, as I use the smart plugs (i.e. for the Christmas lights) for something else in the meantime and they get a reset. I donāt want to delete the flows, because this way, I only have to add the smart plugs again next Christmasā¦
Hey @Henk_Renting ,
I didnāt implement that option right now.
Iāll have a look if I can add that 
Would be great. Thanks for the quick reply and looking in to it!
I would suggest to keep it simple and replace these devices in āSeason flowsā with fe < Group > Virtual Devices . Next year you only need to āAssociateā these Virtual Christamstree Switch with the Temp paired Switch.
That a Virtual Device isnāt direct connected will not break flows.
I donāt see how that would make it any simplier.
Just resetting the devices and exclude a flow folder āChristmasā would be far easier in my opinionā¦
@Dijker @Henk_Renting
I think itās a good idea, Geurt, and it gave me an idea.
If I may āinterfereā
,
I also think a < group > device is simpler imho, while you donāt need additional flows.
Example:
- Original flow:
Ifā¦
Xmas tree trigger
Andā¦
X-mas master switch is on
Then
āXmas plug Yā - turn on
Now this flows breaks when the āXmax plug Yā is removed.
When you create a group called āXmas_plug_Y_grpā f.i. and you add only the real Xmas plug Yā to that group,
changing the original flow to this flow does the trick:
- Adjusted flow
Ifā¦
Xmas tree trigger
Andā¦
X-mas master switch is on
Then
āXmas_plug_Y_grpā - turn on
Now when you remove the real plug, rename it and use it elsewhere, the flow stays valid.
At next Xmas season, you only have to add that plug to the < group > āXmas_plug_Y_grpā device again.
No need to fix the flow.
Then I need 2 flows for an action I could have done with 1 flow. And for Christmas lighting that I would like to switch separately; living room, balcony, front door, bedroom, etc.
Believe me, it would be far easier to exclude one folder from checking by Flow Checker.
But we"re getting offtopic here⦠
Donāt know what the 2nd flow should do, Henk⦠I only suggest adjusting the existing flow? But itās fine with me, I just wanted to point out āanā approach.
I donāt think itās off topic imho, while we try different ideas to prevent the broken flows phenomenon.
Cheers.
Sorry, see that now. I read too quick. 
Anyway, I think excluding a folder from Flow Checker would be a nice add-on. My example was merely to illustrate⦠
New app update (test: 1.14.0.):
- NEW: add folder filter (excluded from flowcheck)
- NEW: improved settings page
@Henk_Renting added the filter for folders. You can find the folders on the settings page. Also improved the settings page a bit. Because it was quite long already ![]()
Can you test it? ![]()
You are the best @martijnpoppen!
Will surely test and let you know!
Works like a charm here, @martijnpoppen ! Thanks again.
I like the new settings lay-out too!




