@Sharkys this should fix a lot of false positives for you
@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
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
b499b3c1-d62e-4bda-98f4-3b0e9b92108f
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 
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.
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)
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
Yes thatās the 2nd bullet on my todo list ![]()
No more flows with broken variables 
YES! 
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.
@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 did the same thing. You were using v1.1.3 before too?
Because that might be the change






