My thoughts either. I updated as soon as I read about an update during the evening.
Only my last go was only on v1.1.3 I guess.
(I should save more data when testing 
)
Well, it’s fixed now. Thanks again.
Cheers
1 Like
I’ll check tomorrow if other people have any false positives. And after that will push it to live.
Next test update is almost ready… (device variables)
2 Likes
Great!
Do broken string Vars report as expected? Didn’t test it yet.
Edit Just tested and I broke those too 
Yeah they do, It tried them all 
I know!
1 Like
Tested it as well, no errors so far 
2 Likes
My false positives are gone, great and fast work! Thanks!
1 Like
As far as I know all rate limits get released/cancelled after 24hrs
Waking up with a timeline full of “broken” flow notifications. Checked the app itself and no broken flows in the overview.
What could be the “problem”? Not running the test version btw. There are some important flows in there for the smoke detectors, so just to be sure.
New app update (live: 1.1.5.):
- FIX: increase interval to 3 minutes to save RAM
- NEW: Add broken logic variable check
- FIX: Make broken flows checker consistent
- FIX: multi variable in
Thenchecker- FIX: multiple variables inside conditions and action flowcards
*OPT: increment interval for variable check (flow check every 3 minutes / variable check every 30 minutes)
1 Like
@UA84 i would suggest downloading the new live version. It has a couple of fixes for false positives
1 Like
What I saw was when the Shelly app get’s updated, the flows involved get reported ‘broken’, will check if this behavior is gone with the latest live version (1.1.4)
@Martijn_Hoogenbosch I was already afraid that would happen. But it’s only very short time.
If that occurs again I might have some ideas
Just after installing the 1.2.0 version, the Shelly app auto updated too. It did not list the broken flows anymore. So maybe solved. Will keep a close look at it.
1 Like
The Shelly app just got updated to a new version again. Again no broken items listing, I guess it is save to say this problem is solved.
Hi Martijn,
FYI, I got 2 false positive broken vars right after the update to test v1.2.0
(Yeah finally I got a false positive 
)
The vars used come with the “Sun Events” and “Openweathermap” apps.
- This is one of the flows (the THEN parts of both flows are similar):
- The flow output works fine when doing a test run:
1 Like
@Peter_Kawa Awesome! 
Will check
Probably something with multiple device variables at the same time.
1 Like
Cheers hehe. Funny fact, it is the first time after running probably all test versions. The flows are months old and were not altered.
