@martijnpoppen
Thanks for your great help!
1 Like
Hi Martijn,
040127e8-4284-43d5-b80c-0f8ed7ed6fd3 - do you see there anything please, I suddenly got few flows with broken variables but they are fineâŚ
Eg. flow with name âHomey LED on/off advâ :
update Ah, I see it says Screensaver missing - but itâs not.
@Sharkys for what I can see: APIErrorTimeout: Timeout after 5000ms
So looks like some internal error in the app
Is reported as an error anyway, I had that too. I assume that during migration all 3rd party screensaver flow cards are automatically replaced by Athoms flow cards. You only need to change or replace the cards and then save the flow, after that the flows will no longer be detected as broken.
1 Like
Please see my comment on the screensaver⌠or itâs related ?
Thank you, problem is that some of the flows were created already on HP23 ;-( Also checked them and re-saved, didnât help.
In that case I Will disable the screensaver check on HP23 as it probably causes issues.
1 Like
Could it even happen that screensaver is missing / using incorrect one on HP23 ? I just wonder, on HP19 that was different situation I guess. Iâm just surprised I got it suddenly this morning first time.
@Sharkys it might be related to the api error timeout and therefore it wants to check the screensaver but it cant
1 Like
Hi Martijn, on my hp 2019 all flows in which I set the screensaver to âweatherâ are marked as broken variable. Iâve created a simple flow to test this
Please, this is the english forum.
2 Likes
@Jan_Albert Will check
Hi Martijn,
Pro 2019 v8.1.6
app v1.23.6
I noticed this possible bug a while ago already, hereâs my FC overview:
All my flows are reported as broken, and there are more broken flows reported than âALL Flowsâ shows 
The actual flows show their normal broken or not status:
As always, no hurries!
@Peter_Kawa yeah the broken check is broken 
Athom made a change for webapi v3 and i tried to implement it last week but it gives massive memory issues.
Im waiting for a response from them
So the check right now does nothing so it will never fix itself thats why you see a wrong number there.
Hopefully a fix is available soon 
2 Likes
I see, thanks for the quick response!
1 Like
I suspect Athom is doing something with the API (or itâs firmware change) because for last 3 days I was getting notifications about disabled flowsâŚtoday, I got first time ever on HP23 notification about broken variable and - it was correct ! @martijnpoppen , any news on that, have you seen something similar ? Btw I was on 1.22.2, testing now the 1.23.6
update back on 1.22.2 as with 1.23.6 all flows are marked as broken 
1 Like
@Sharkys Not that iâm aware of. The isbroken check is still broken 
But working on it with Athom
1 Like
New app update (live: 1.24.2.):
1. NEW: isBroken check for Homey API v3
If you find any issues, send a report via the mobile homey app
More - apps - Flow Checker - settings wheel right top - send diagnostic report (put your email in the input field to make it easier)
New app update (live: 1.25.0):
1. REVERT: isBroken check. crashing app on some homey versions
If you find any issues, send a report via the mobile homey app
More - apps - Flow Checker - settings wheel right top - send diagnostic report (put your email in the input field to make it easier)
1 Like
Will investigate the issue with Athom 
Thanks all the zwave issues i had to exclude / include various aeotec smart switches
I use the in dozens of flows
This means that with all these flows cards are missing and show a â?â I think
Its 2023 so i think Athom should mark those flows !!! They did in older app versions ( think a ! Was shown at the flow with a missing card )
Anyway
I installed flow checker to check for errors in my flows. But i do not see the flows with the missing cards show up ??
That is a flow with an error I supose.
So all those flows should be visible in the flow checker app ⌠right ?
