[APP][Pro] Flow Checker

[martijnpoppen]

Good one @Peter_Kawa ,
Will change that.

[Peter_Kawa]

Maestro, maybe you’d noticed it alr, but the title of “Unused Variables” went missing.
And the summary description for this changed to ‘settings.unused_logic’
(the total # of unused vars is still correct).
v1.11.0

Cheers!

[martijnpoppen]

New app update (test: 1.11.1.):

• FIX: locale issue

@Peter_Kawa Fixed

[martijnpoppen]

New app update (test: 1.12.0.):

• NEW: add folders to flow notification and settings

Notification:

Settings page (bold text is folder)

---

CC: @Homey-Cornelisse

[Peter_Kawa]

[Jan_Willem_Visser]

I have a question:

I use the trigger card “this flow has started” a lot, so this ensures that the list of unused flows is very long for me, which is actually incorrect.

Is there a way to not show these flows in this list?

Regards Jan Willem

[Niels_Veldman]

I use the live version 1.11.1

I have flow A that starts flow B.
I have deleted flow B.

Flow A still shows ‘Start Flow B’

Should your app detect that flow A is now ‘corrupt’?

[martijnpoppen]

Hey @Jan_Willem_Visser ,
I’ll check that, it should only report the flows which are not started by another flow.

[martijnpoppen]

Hey @Niels_Veldman ,
Actually the other way around. So if you delete flow A it would show flow B as unused.

I’ll check the possibilities for this. Maybe mark the flow as 'broken' as the linked flow doesn’t exist.

This is not something I’ve implemented yet.

Will add that to the todo list

[Jan_Willem_Visser]

I’ve checked everything but can’t find any flows that aren’t started by another flow.

Since it concerns almost 190 flows in the list, it does not seem to me that all of them would never be started

In addition, there are important flows that do their job many times a day. So it seems that they are actually incorrectly listed.

[Rocodamelshekima]

Any ideas?

[martijnpoppen]

@Rocodamelshekima yes

See [APP][Pro] Flow Checker - #4 by martijnpoppen FAQ Q2

So Homey cannot deal with to many flow triggers

[Rocodamelshekima]

Ah ok. So it should only happen the first time and not when just a few flows was disabled. Gonna watch it closely because I don’t think this was a first time run.
Thnx for the answer.

[martijnpoppen]

@Rocodamelshekima it happens when a big amount of flows changes. For every flow theres a trigger. Which can cause this. So of you have a lot of flows the limit is reached faster.
I’m not sure how many triggers cause this limit.

[Rocodamelshekima]

Well, it’s like more then 10 times in a second. But I keep an eye on it, cheers

Must say there was a few flows disabled at that specific time.

[martijnpoppen]

Yes! that’s for every flow it wants to report. So only if you made a flowcard for flowchecker.

Did you start using the app 2 days ago?

I still want to find a way to fix this.
I’ll put a maximum on the trigger within a minute. Maybe that will fix this issue.

[Homey-Cornelisse]

Thanks for adding this feature, will save a lot of searching.

[martijnpoppen]

New app update (live: 1.12.3.):

• FIX: rate_limit issue ( @Rocodamelshekima )
• FIX: unused flows only show unused (@Jan_Willem_Visser )
• FIX: German language (thanks to @DirkG )

[Jan_Willem_Visser]

Thank you verry mudge for the update, works great now.

[ArnarS]

Hi. Great app.

I have a suggestion for a new feature in your app, which concerns the issue when you rename flows. Obviously, it is an issue Athom should adress, but… you how that can go.

So the issue is that when you rename a flow which is part of a chain of flows, the parent flow’s ‘then’ card doesn’t get updated with the new name. So when you go into the parent it will show the old name and then it becomes really difficult to maintain your flows.

Could your app come with a notfification like: “Flow A started Flow C, which used to be called Flow B” ?