@Sharkys this should fix a lot of false positives for you
1 Like
@martijnpoppen unfortunately it’s not the case but let’s see results of others testing it
If it helps :
015c572f-7d0a-4b83-9679-b95e29b0317e
Have a good night! 
Thanks! The multiple variables inside a Then card are catched right now.
Working on the If + And cards now to support multiple variables
1 Like
I can’t produce a broken variable. 
Renaming or deleting one is not registered.
How do I brake one to test it?
(The app reports no broken variables )
No false positives here by the way
deleted variable:
renamed variable (flow works as before renaming it)
app (all 3 V’s are blue):
Thanks for all your efforts!
2d97718c-d5a0-4f69-8161-4538dd0f7188
1 Like
b499b3c1-d62e-4bda-98f4-3b0e9b92108f
1 Like
I made multiple flows with a test variable. Everytime I put the variable somewhere else (trigger/condition/action). Then I removed the variable from the logic.
And then everything breaks 
Actually I was expecting that you would have a lot of broken variables (false positives)
As the previous test with disabled/broken triggered a rate_limit 
Will try that!
I’m good with variables so it seems 
Let me show you why I got a rate limit 
Am I the only one with ‘some’ broken and disabled flows? 
Hehe no suprise there 
I saw the How much can a non pro handle topic.
Maybe for a future update: Would it help if the flows are categorized in that overview? Because I can get the parent folder name of the flow.
1 Like
New app update (test: 1.1.3.):
- FIX: multiple variables inside conditions and action flowcards
New update which hopefully fixes the false positives (at least most of them)
4 Likes
My Homey has to work 
hehe.
That would be great.
Is it also possible to produce a total no. of broken and a total of disabled flows?
Or / and a numbered list?
Just a brainfart
No more flows with broken variables
YES! 
Whoops!
Still can’t get anything to break with testflows and testvars. Tried moving around, saving flow, deleting var
I happen to use a True/False var, was someone able to break that particular var type?
Yes I broke a var!
A deleted numVar gets reported
1 Like
I’ll check the Boolean vars. They should work 
Luckily you broke something !
Finally! Took me hours
And curious if it’s a problem with the bool vars.
1 Like
@Peter_Kawa tried with a boolean. Result: broken variable.
I’m using the webapp. Maybe that makes it different?
Edit: I tried the Then card. I see you use the condition card. Will test that too
Edit 2: Still reports broken:
I use the phone app.
Flow Checker app v1.1.3
I really don’t know what’s different, but now it gets detected !
The only thing I used a “flip a bool” card in addition, earlier I used only “set to true” and “set to false” cards
Flow:
I did the same thing. You were using v1.1.3 before too?
Because that might be the change
