You too!
If it happens again let me know ! 
1 Like
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
1 Like
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
2 Likes
Thanks for solving that small mystery 
2 Likes
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âŚ
3 Likes
Hey @Henk_Renting ,
I didnât implement that option right now.
Iâll have a look if I can add that 
1 Like
Would be great. Thanks for the quick reply and looking in to it!
1 Like
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.
2 Likes
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âŚ
1 Like
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? 
3 Likes
Works like a charm here, @martijnpoppen ! Thanks again.
I like the new settings lay-out too! 
2 Likes
