The variables which were previously marked as “Unused Logic Variables” are no longer listed in this category. 
Thx Martijn!
1 Like
Awesome! 
1 Like
Just installed it, Martijn. Cool, it went from 12 to 5 “unused” vars!
And the last 5 really were unused, so I removed them right away.
Over 19MB’s while the checks run you mean? 
. It’s ~15MB average by the way.
Yea I’ll keep an eye on it.
Good stuff 
19MB is still okish.
When you see what kind of code is running 
1 Like
I believe you 
hehe
The interval is set to 60mins , I was playing with that setting to lower the RAM usage as much as possible.
Allright, about the load with v1.16.0:
It looks like it grew 4 to 5 MB’s, 18 to 19MB’s average. Still OK!
1 Like
Yes was expecting that. It added quite some more load. I’ll check if I can tweak it a bit 
1 Like
New app update (live: 1.16.0.):
- NEW: find nested logic variables in other apps THEN cards to prevent false positives
Will take the memory tweaks along with the other feature requests
1 Like
I don’t have such big memory peaks. The peaks are more or less 1 MB.
I couldn’t also recognize no increasing of the average load.
Here’s no complaint: it’s running 17.5MB now, interval = 60 
1 Like
Hi!
Would it be possible to monitor status of performed actions? E.g. if I tries to turn on an unreachable swich I will, after 30 s, see a banner in the Homey app notifying me of the unsuccessful status. Is this possible to monitor and create a flow trigger?
Hey @Anders_Gregow
Nice Idea
I’ll check the possibilities
Will be something like a flow failed
3 Likes
Nice, thanks.
Maybe also a check if a device becomes invalid?
1 Like
Hi @martijnpoppen , I was just deleting one of the devices and was hoping that Flow Checker will trigger alert (at least I really think I used it somewhere ). But seems it’s not the case, more over I see old broken flows, which I fixed. Can you check, if there is anything wrong?
7f006772-5213-46b5-9cfb-8ae1053c8157
Also got this error when enabling flow checks on start - 2nd attempt was already ok.
Thank you.
Checked the logs but nothing strange there
About the API error that sometimes happens when the app is still starting and the settings are not ready yet.
I’ll make a loader for that someday
1 Like
Did the update solve your problem? I am getting a similar message as well…
TypeError: Cannot read properties of undefined (reading ‘includes’)
Edit: okay, it’s obviously late - the message is not similar at all.
Does anyone have any idea how to solve this one?
Hey @dzt
Not sure where that came from
Can you share a diagnostic report?
More - apps - flowchecker - settings wheel right top - send diagnostic report
Hi Martijn!
Thank you very much. I’ve created a raport few moments ago.
I’ve reinstalled the app. It’s been this way from my first install few days ago.
14d702bd-2e96-4cdb-8df0-959d4c4b1d93
Best regards
1 Like
Hey @dzt
Can you try to restart the app
Looks like it’s missing some config. 
That should be fixed on startup.
1 Like
