Hey @ArnarS !
I’ll look into that! Good suggestion.
Will come back when I have found a way to do so.
Hey @ArnarS !
I’ll look into that! Good suggestion.
Will come back when I have found a way to do so.
And another request:
Get the flows bij folder tree.
Now I only get the flow name but not in what folder it is.
Ah ok. Missed that, cheers!
@martijnpoppen, after updating Homey to experimental firmware v7.2.0-rc.2 today 20 flows were shown in the timeline as broken. But the most of them are productive flows which ran every day. So I looked into the settings of the app.
Broken Flows: 250
Deactivated Flows: 180
But this was absolutely not true. So I updated via “Update broken flows and variables” action card. After updating everything seems to be ok now.
Don’t know if it was a problem of the Homey FW update or if it’s a bug in your app.
Diagnostic report no.: 301d976e-bfbc-4867-878c-2e689acebf18
Hey @DirkG ,
It might be that flowchecker was the first app that was started, What interval did you set up for your flows?
There’s a 10 second timeout on the start of the app. But in case of a Homey restart/install that might be not enough
That seems to be the explanation.
180 minutes
Hmm yes. Then it was the startup of the app.
Thinking out loud:
Maybe I should remove the flow check on the app startup and only update the flows with interval And/Or flowcard.
Yes please, or make it an option with a default to off
- NEW: add ‘Run flow check on startup’ to settings. Prevent false positives after Homey Reboot
So with this fix.The flow check is not started on launch of the app.
(This will default be disabled for everyone.)
Example:
Interval of 3 minutes - The first interval will start after 3m 25s after the app has started.
When you enable flowcheck on startup:
Installing now… thanks!
- NEW: add ‘Run flow check on startup’ to settings. Prevent false positives after Homey Reboot
Hi Martijn,
Homey v7.2.0
FlowChecker v1.13.0
I’ve a small “issue”:
after deleting a broken or a disabled flow, a notification is generated, like “Flow X became active”
Cheers, Peter
Hey @Peter_Kawa ,
Probably you made that notification
Because the app is in english only.
There’s a flow card for when a flow became active again, but no notification.
However your point is valid. That flowcard shouldn’t be triggered if the flow gets deleted. Not sure if that’s easy to fix though
Ah! You’re right
Found it:
But don’t break your head over it. It’s just a minor itch!
First of all, very useful app! Thanks for that! However, it doesn’t work properly on my Homey (7.2.0). I can’t save settings, and get an error:
TypeError: undefined is not an object (evaluating ‘unsafe .replace’)
Could you help me please?
I’ve restarted the app multiple times, no result. Let me uninstall and reinstall it.
Yeah really hard to debug.
But i’ll check the code if I can find something related to your error
Reinstalling the app did the trick. Thanks anyway for your effort and quick replies. Have a nice weekend!