That sounds like some next level Sherlock Holmes-stuff 
. Glad that you both were able to track down and solve the issue.
Hmm i can’t figure out why my advanced flows are lagging.
Hi John William,
Where is the screenshot coming from?
Do you use https://my.homey.app, or the local editor http://homey.ip.address/ ?
I use my.homey.app the screenshot is from the Network console shown in your screenshot.
Which request is it for? For a binary file/script? Then it’s completely normal.
I’ll check again tomorrow, about to sleep now. 
programmatic_trigger?
Is it a SocketIO message? That’s normal, it just returns all available Flowcards.
That’ll be a triggercard (guessumption).
Could it be a “When device is X during Y [time unit]” flow card?
What info (below the listing) is presented when you tap/click that paricular entry?
That’s normal. The Web App loads every Flowcard at once, instead of “lazy loading” which most websites use. So every single Flowcard is loaded at once on the Homey webapp. I also don’t understand why it does that, but that’s a design decision from Athom
Oh alr
Live with it.
It is a long standing problem of sluggish implementation and as things stand today Athom will probably not adress it in any forseeable future.
This was caused by some Homey apps extensively calling setCapabilityOptions, which caused Flowcards to get re-created. Which apps do you use on your Homey? And are they all on the latest version?
